Remove strict mode from market commands#9
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This removes the strict-mode flow for empty market responses from end to end.
I removed CLI support for
--strict(global andhistory/chaincommand flags), deleted strict-driven daemon validations that previously raised errors on empty bars or chain results, and droppedstrictfrom market command schema and payload handling.I also removed strict parameters from SDK market methods (Python + TypeScript), updated CLI/docs references so the feature is no longer advertised, and removed the obsolete daemon test that expected strict history failures on empty data.
Co-authored-by: Bryce Bjork brycedbjork@gmail.com