Prevent crash in some user backend methods #1251
Merged
Conversation
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
…d from bad interfaces) when provided params have the wrong type, make UserMapper methods stricter and cleaner, add a few missing query param types Signed-off-by: Julien Veyssier <[email protected]>
julien-nc
changed the title
solracsf
reviewed
Nov 13, 2025
solracsf
reviewed
Nov 13, 2025
solracsf
approved these changes
Nov 13, 2025
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.
Those methods are inherited from bad interfaces.
We now prevent a crash when provided params have the wrong type. This is not supposed to happen but it did according to #1238.
Also make some UserMapper methods stricter and cleaner and add a few missing query param types.
closes #1238