-
Notifications
You must be signed in to change notification settings - Fork 477
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
Expand HAL-FORMS to handle immutable types properly regarding "readOnly" status #1282
Labels
in: mediatypes
Media type related functionality
Comments
Hello @gregturn , Can I contribute with a pull request? I have some questions about the hint annotation:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's possible to create an immutable type where you have no setters. Instead, everything is built upon either constructor calls or "@With" or whatever, and the existing code would PROBABLY misread the "readOnly" nature of those types.
We need to expand the existing set of unit tests to cover such scenarios, and then potentially entertain a "hint" annotation that could be applied to properties, constructors, and even getters/setters. That way, Spring HATEOAS can try to guess as best as it can, but in the corner cases where it can't figure it out, grant users ability to mark up their code to help HAL-FORMS render things as desired.
Related issue: #1274.
The text was updated successfully, but these errors were encountered: