Expose current price monitoring bounds via MarketData API #2680
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
…e validation to hold proposal in a slice so we keep their execution order deterministic
…unds requirements
EVODelavega
reviewed
Dec 2, 2020
cdm
reviewed
Dec 3, 2020
cdm
reviewed
Dec 3, 2020
jeremyletang
approved these changes
Dec 4, 2020
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.
To aid testing (and give users a chance of understanding when price monitoring is triggered) we want to expose price monitoring bounds - the actual min/max valid prices per trigger for the current timestamp.
Closes #2667