Skip to content

Document correct behavior for AttributeConverterProvider #2353

@chrylis

Description

@chrylis

I am attempting to write a custom AttributeConverterProvider for handling a specific type, and I intend to use it in conjunction with DefaultAttributeConverterProvider as described in the documentation. However, the Javadoc for AttributeConverterProvider#converterFor(EnhancedType) does not specify the correct behavior when my custom converter is asked about an unknown type (i.e., a built-in). The only example is the default implementation, which throws on an unknown type, and this does not seem like the correct behavior. Should I simply return null? (ChainConverterProvider suggests this.)

The Javadoc needs to cover the case for "not found".

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions