Add synthApi (#27)
* Add synthApi * Put confidence for Synth proba * Update the code * Update readme * Fix bootstraping * fix github build * Update the endpoints for scenario * Add scenario and update backtest modal * Update bot modal * Update interfaces for synth * add synth to backtest * Add Kelly criterion and better signal * Update signal confidence * update doc * save leaderboard and prediction * Update nswag to generate ApiClient in the correct path * Unify the trading modal * Save miner and prediction * Update messaging and block new signal until position not close when flipping off * Rename strategies to indicators * Update doc * Update chart + add signal name * Fix signal direction * Update docker webui * remove crypto npm * Clean
This commit is contained in:
@@ -103,7 +103,7 @@ Key Principles
|
||||
- Before creating new object or new method/function check if there a code that can be called
|
||||
- Most the time you will need to update multiple layer of code files. Make sure to reference all the method that you created when required
|
||||
- When you think its necessary update all the code from the database to the front end
|
||||
- Do not update ManagingApi.ts, user will always do it with nswag
|
||||
- Do not update ManagingApi.ts, once you made a change on the backend endpoint, execute the command to regenerate ManagingApi.ts on the frontend; cd src/Managing.Nswag && dotnet build
|
||||
- Do not reference new react library if a component already exist in mollecules or atoms
|
||||
|
||||
Follow the official Microsoft documentation and ASP.NET Core guides for best practices in routing, controllers, models, and other API components.
|
||||
|
||||
Reference in New Issue
Block a user