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

Hilla should tolerate classes using only one of @JsonValue and @JsonCreator #3095

Open
cromoteca opened this issue Dec 30, 2024 · 0 comments · May be fixed by #3097
Open

Hilla should tolerate classes using only one of @JsonValue and @JsonCreator #3095

cromoteca opened this issue Dec 30, 2024 · 0 comments · May be fixed by #3097
Assignees
@cromoteca
Labels
enhancement New feature or request hilla Issues related to Hilla

Comments

@cromoteca
Copy link
Contributor

Describe your motivation

There are use cases for one of those annotations being used without the other one. See for example How to force Hilla not to consider java class with @JsonCreator as single-value?

Describe the solution you'd like

Such classes are not interpreted as domain objects and are treated as usual.

Describe alternatives you've considered

No response

Additional context

No response
@cromoteca cromoteca added enhancement New feature or request hilla Issues related to Hilla labels Dec 30, 2024
@cromoteca cromoteca self-assigned this Dec 30, 2024
@cromoteca cromoteca linked a pull request Dec 30, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cromoteca cromoteca

Labels
enhancement New feature or request hilla Issues related to Hilla
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: allow classes with one of JsonValue and JsonCreator to be generated vaadin/hilla
1 participant
@cromoteca