Skip to content

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

@cowtowncoder

Description

@cowtowncoder

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.xIssues to be only tackled for Jackson 3.x, not 2.x

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions