-
Notifications
You must be signed in to change notification settings - Fork 5
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
Backend upgrade 4.x #175
base: main
Are you sure you want to change the base?
Backend upgrade 4.x #175
Conversation
Signed-off-by: montesm <[email protected]>
Signed-off-by: montesm <[email protected]>
This will be a nice QOL enhancement 👍 I've tried to use a record so many times only to remember that we're on java 11. |
Signed-off-by: montesm <[email protected]>
Signed-off-by: montesm <[email protected]>
Signed-off-by: montesm <[email protected]>
Signed-off-by: montesm <[email protected]>
This reverts commit 8d3a767 Signed-off-by: montesm <[email protected]>
Signed-off-by: montesm <[email protected]>
Signed-off-by: montesm <[email protected]>
private List<ServiceDefinitionAttributeDTO> buildUserResponseAttributesFromRequest(HttpRequest<?> request, List<ServiceDefinitionAttribute> serviceDefinitionAttributes) { | ||
|
||
Argument<Map<String, String>> type = Argument.mapOf(String.class, String.class); | ||
Optional<Map<String, String>> body = request.getBody(type); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@HootDunk After migration, I found that body
was null. I suspect it is due to the following breaking change outlined in https://docs.micronaut.io/latest/guide/#_body_annotation_on_controller_parameters .
I resorted to deserializing the request body to a Map so that we have access to the attribute[attrValue]
form keys.
Required: Install Java 17