fix: handle null name parameter in user creation endpoints #11215
+24
−24
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.
What does this PR do?
Fixes #8785
Problem
When a client explicitly sends
name: nullin the request body to any of the user creation endpoints (POST /v1/users, /v1/users/bcrypt, /v1/users/md5, etc.), the API returns a vague server error instead of handling it gracefully.Solution
The
nameparameter now uses theNullablevalidator wrapper (consistent withemailandphoneparameters that already handle null values):new Text(128)tonew Nullable(new Text(128))string $nameto?string $name$name ?? '') when passing tocreateUser()functionAffected Endpoints
Testing
name: nullnow creates user with empty name (same as not sending name at all)name: "John"works as beforeRelated Issue
Fixes #8785