add sub account optional flag #414
Merged
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
ningcb
reviewed
Jun 8, 2022
ningcb
reviewed
Jun 8, 2022
ningcb
approved these changes
Jun 8, 2022
|
Review Error for ningcb @ 2022-06-08 20:38:36 UTC |
irisZhangCB
approved these changes
Jun 8, 2022
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.
Fixes #403 .
Motivation
In some rosetta implementation
sub accountfield is optional. This means we can't predict if it will be there or not. The current matcher logic requires it to be either required or not required.Solution
Added a flag called
SubAccountOptionalwhich if set totruewill ignore the subaccount matching and if false, behaves exactly as beforeOpen questions