-
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: AssetEnabled upgrade #1735
base: master
Are you sure you want to change the base?
Conversation
3697ede
to
5fb08d2
Compare
026f88f
to
272827a
Compare
942b49b
to
e2d81d0
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick test on gateio, when I set everything but spot assets to false for asset enabled it still fetches and subscribes all assets. Doesn't seem to be happening on master, once resolved I will do a more in-depth check.
c092bfa
to
65c05a0
Compare
Fixed gbjk@65c05a063 |
65c05a0
to
4a4fb99
Compare
Config:
Exchanges:
StoreAssetPairFormat
toStoreAssetPairStore
SetAssetEnabled
will not error on no-op (already disabled or enabled)Bitfinex:
Type of change
Please delete options that are not relevant and add an
x
in[]
as item is complete.How has this been tested