Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ensure primitive type names in error message enclosed in backticks #492

Closed
cowtowncoder opened this issue Oct 20, 2018 · 0 comments
Closed

Ensure primitive type names in error message enclosed in backticks #492

cowtowncoder opened this issue Oct 20, 2018 · 0 comments
Labels
3.x

Comments

@cowtowncoder
Copy link
Member

Error messages should contain "code" symbols like class names in backticks (wiki style), and this has been done in many places. But at least overflow exception messages use unquoted names ("out of range of long" etc). Let's unify that for 3.0.
@cowtowncoder cowtowncoder changed the title Ensure primitive type names in error message enclosed in backticks (jackson 3) Ensure primitive type names in error message enclosed in backticks Oct 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.x
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cowtowncoder