Workaround: fix #404 updating api for user data #409
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
lipkau
force-pushed
the
fix/#404-UpdatingApiForUserData
branch
from
4204bed
to
f7e04b7
Compare
|
don't you think there will be much more issues with latest rather than certain number? I guess it should be exact api number by default and chaging it is a major change |
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.
Description
workaround
temporarily changed api routes to use version 2.
This should be reverted to version
latestas soon as a proper handling of how users work between cloud and on-premise is implementedMotivation and Context
closes #404
Types of changes
Checklist