[stable-5.2] fix: Fire UserChangedEvent only after change happenned#877
Merged
juliusknorr merged 1 commit intostable-5.2from Aug 16, 2024
Merged
[stable-5.2] fix: Fire UserChangedEvent only after change happenned#877juliusknorr merged 1 commit intostable-5.2from
juliusknorr merged 1 commit intostable-5.2from
Conversation
This is not a before event, so the user should already have been changed when it fires. Should fix issues with dav address book and newly mapped saml users. Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
juliusknorr
approved these changes
Aug 16, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Backport of PR #873