fix: Treat example values starting with numbers as strings (#4999) #5021
+121
−7
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.
Pull Request
Thank you for contributing to swagger-core!
Description
This PR fixes an issue where example values that begin with a digit (e.g., "5 lacs per annum") are incorrectly parsed as a numeric literal instead of a string.
The root cause was that Json31.mapper().readTree(...) interprets any string that starts with a digit as JSON numeric content, resulting in the loss of the remaining string.
What this PR changes
Updated AnnotationsUtils#getSchemaFromAnnotation to ensure that example values beginning with digits are always treated as strings.
Added a test case testExampleStartingWithNumberShouldBeString to verify the expected behavior.
Fixes: #4999
Type of Change
Bug fix
Tests
Checklist
Example before the fix:
"example": 5
After the fix:
"example": "5 lacs per annum"