-
Notifications
You must be signed in to change notification settings - Fork 67
Add more options to deal with localpart conflicts on upstream OAuth 2.0 logins #5295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
sandhose
merged 6 commits into
main
from
quenting/upstream-oauth/better-conflict-options
Dec 3, 2025
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ffb86f6
Add more options to deal with localpart conflicts on upstream OAuth 2…
sandhose 9650dc1
Add tests for the new on_conflict options
sandhose f0d84a4
Document the new conflict options
sandhose c5ba1f6
Check for the new on_conflict options & update docs
sandhose 8384a5a
Merge branch 'main' into quenting/upstream-oauth/better-conflict-options
sandhose 7bfeef9
Typos and error message rewording
sandhose File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not the hugest fan of calling this
Setbecause it doesn't give off any vibe as to what it means. MaybeSetNew, kinda likeOpenOptions::create_new?Or
SetIfNotExistskinda like SQLCREATE IF NOT EXISTS(even though now that I think about it, that's not great grammar :D)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Errr I don't know; at the same time,
setis probably the option which makes most sense in most cases, so I don't want it to look long and complicatedThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that as long as it's documented, it's fine… I can't really think of another single word to better express it?