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.

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

Introduce SmartHttpMessageConverter #33118

Closed
sdeleuze opened this issue Jun 28, 2024 · 0 comments
Closed

Introduce SmartHttpMessageConverter #33118

sdeleuze opened this issue Jun 28, 2024 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@sdeleuze
Copy link
Contributor

SmartHttpMessageConverter adresses several GenericHttpMessageConverter limitations, while providing a contract more consistent with WebFlux Encoder and Decoder, with the following differences:

  • A ResolvableType parameter is used instead of a Type one.
  • The source (MethodParameter today, maybe KType tomorrow) can be retrieved via the ResolvableType source.
  • No contextClass parameter (can be deduced from the MethodParameter).
  • A @Nullable Map<String, Object> hints additional parameter for write and read methods.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant