tier1 always be None in GET tier config request for level 2 #71
Conversation
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
Without having null allowable SDk will throw the following error
TypeError: Invalid structure for initialization of `TierConfigRequest`.
Error: {0: {'tiers': {'tier1': ['Field may not be null.']}}, 1: {'tiers': {'tier1': ['Field may not be null.']}}}.
Because in t2 config request t1 account always be none as per api result from connect platform
Codecov Report
@@ Coverage Diff @@
## master #71 +/- ##
=======================================
Coverage 92.73% 92.73%
=======================================
Files 67 67
Lines 1900 1900
=======================================
Hits 1762 1762
Misses 138 138
Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Without having null allowable SDk will throw the following error
TypeError: Invalid structure for initialization of
TierConfigRequest.Error: {0: {'tiers': {'tier1': ['Field may not be null.']}}, 1: {'tiers': {'tier1': ['Field may not be null.']}}}.
Because in t2 config request t1 account always be none as per api result from connect platform