fix aftermath of #3716 #3722
Merged
fix aftermath of #3716 #3722
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
Signed-off-by: dartcafe <[email protected]>
|
/backport to next |
Signed-off-by: dartcafe <[email protected]>
Signed-off-by: dartcafe <[email protected]>
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.
Rename userId as a follow up on renaming a share's userId
This covers the situation, where a userId of a share is changed, but there are already existing votes, comments or options belonging to the renamed user.
This situation could occur, if a user already registered before the update to 7.2.4 and
already voted, commented or suggested an option and reenters the poll with an email or contact share
Follow up to #3716