borinquenkid commented on PR #16414: URL: https://github.com/apache/grails-core/pull/16414#issuecomment-5882362654
Following up on the custom-serializer gap above: this is 9.0.x, so the fix doesn't need to be bulletproofing \`registerObjectMarshaller\` against every nested custom Jackson serializer — that's a compatibility guarantee worth breaking on purpose here, not preserving by accident. The registered \`JsonMapper\` is the standard Spring pattern (that's what my repro used), and once an app hands Jackson a serializer, Jackson owns what's reachable from it — that's a reasonable 9.0 stance. It just needs to be a stated decision, not a silent one: a line in the 9.0 upgrade guide that a value nested inside a custom Jackson serializer renders as Jackson renders it, not through Grails marshallers, so apps relying on \`registerObjectMarshaller\` for something like redaction know to also handle it as a Jackson serializer if it can show up under a custom one. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
