-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Unwrapped fields cannot be resolved in the constructor #4491
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
Comments
This sounds pretty much like a bug where we do not consider the proper conversion path. |
mp911de
added a commit
that referenced
this issue
Sep 1, 2023
mp911de
added a commit
that referenced
this issue
Sep 1, 2023
Return the value to set instead of calling the accessor directly. Remove duplicate calls to resolve associations. See #4491
christophstrobl
pushed a commit
that referenced
this issue
Sep 11, 2023
Return the value to set instead of calling the accessor directly. Remove duplicate calls to resolve associations. See #4491
christophstrobl
pushed a commit
that referenced
this issue
Sep 11, 2023
Remove sysout from tests. See #4491
christophstrobl
pushed a commit
that referenced
this issue
Sep 11, 2023
Return the value to set instead of calling the accessor directly. Remove duplicate calls to resolve associations. See #4491
christophstrobl
pushed a commit
that referenced
this issue
Sep 11, 2023
Return the value to set instead of calling the accessor directly. Remove duplicate calls to resolve associations. See #4491
christophstrobl
pushed a commit
that referenced
this issue
Sep 11, 2023
Remove sysout from tests. See #4491
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am designing a domain object using @unwrapped, but the constructor fails to resolve the Unwrapped Field (age).
Error Message
I've checked with @Vaule and SpEl that it's possible to use the code below, but I don't think it's a good idea. Is there any way to automatically resolve unwrapped fields in the constructor?
The text was updated successfully, but these errors were encountered: