Ignore malformed language ranges when resolving locales for validation #33216
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.
Fixes #33150
additionally, I've tried to make both
AbstractLocaleResolver
andSmallRyeGraphQLLocaleResolver
look even more similar.As for logging a message, I thought since it's not a validation error caused by bad values in the request body, and (hopefully) in most cases, headers aren't typed by users 😃 but generated by an API client, that would indicate a problem in a client, which is more of a dev problem... so they might want to see it 😃
I didn't see any locale-/validation- specific tests in
quarkus-integration-test-hibernate-validator-resteasy-reactive
orquarkus-integration-test-smallrye-graphql
so I haven't introduced any new ones there ...