feat: show buy/sell order details in the grid trade sections #527
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@rando128 |
|
@chrisleekr is this added to the main release? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Improve the frontend with information about the recent orders that took place in the current grid trading.
Motivation and Context
Today there is no way to get the details of buy and sell orders that the bot executed in a specific coin grid. This PR is about showing the date, price, quantity and amount for each buy/sell order happening in an active trading grid.
How Has This Been Tested?
This PR simply expands the grid trade sections with order details ( date, price, quantity, amount) only when the grid got executed. This has been tested on my local setup with multi-grid coins.
I couldn't write tests as I couldn't find existing tests dealing with UI aspects that I could reuse.
Screenshots (if appropriate):