User status key error #615
Closed
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
vossen-adobe
approved these changes
Jun 15, 2020
|
@nickila Please create an issue for this and link it to this PR by adding a "fixes #xxx" line to the description. We need tracking issues for all PRs so we can track and triage bugs appropriately. |
vossen-adobe
added a commit
to vossen-adobe/user-sync-fork
that referenced
this pull request
Sep 18, 2020
|
This can be closed as it was a UMAPI issue that should be resolved now |
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.
Fixed bug that would throw error when userStatus wasn't present as a key. Now it will allow the user to be included if the key is missing. Also wrote a unit test for that aspect of the get_users method.
fixes #643