fix(provisioning_api): read newUser.sendEmail as a boolean - #62776
Merged
Conversation
Signed-off-by: Peter Ringelmann <peter.ringelmann@nextcloud.com>
pringelmann
requested review from
leftybournes,
nfebe and
salmart-dev
and removed request for
a team
August 3, 2026 07:26
CarlSchwan
approved these changes
Aug 3, 2026
susnux
approved these changes
Aug 3, 2026
Contributor
Author
|
/backport to stable34 |
Contributor
Author
|
/backport to stable33 |
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
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.
Summary
newUser.sendEmailis written as a typed boolean since #57079, but both user creation paths still compared it to the stringyesTODO
stable34andstable33Checklist
3. to review, feature component)stable32)AI (if applicable)