-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config: OrderManager upgrade #1737
Open
gbjk
wants to merge
11
commits into
thrasher-corp:master
Choose a base branch
from
gbjk:feature/config_ordermanager
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
gbjk
added
the
nomerge requires dependency
This pull request is dependent on another, so it can't be merged until the dependent one is merged
label
Dec 4, 2024
gbjk
changed the title
Config: Move OrderManager to version management
Config: OrderManager upgrade
Dec 4, 2024
gbjk
force-pushed
the
feature/config_ordermanager
branch
from
December 9, 2024 08:14
76a5f04
to
9b7b71e
Compare
This became more messy with Disabling something that's defaulted to disabled. Taking an idealogical stance against erroring that what you want to have done is already done.
Previously we were calling it "Format", but accepting everything from the PairStore. We were also defaulting to turning the Asset on. Now callers need to get their AssetEnabled set as they want it, so there's no magic This change also moves responsibility for error wrapping outside to the caller.
Previously we ignored the field and just turned on everything. I think that was because we couldn't get at the old value. In either case, we have the option to do better, and respect the assetEnabled value
gbjk
force-pushed
the
feature/config_ordermanager
branch
from
December 12, 2024 04:38
9b7b71e
to
7b8726d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
nomerge requires dependency
This pull request is dependent on another, so it can't be merged until the dependent one is merged
review me
This pull request is ready for review
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.
*bool
with a boolean inorderManager.Enabled
andorderManager.RespectOrderHistoryLimits
FuturesTrackingSeekDuration
with positiveStacked Dependencies
Type of change