Brian Clozel

We've discussed this issue as a team and we can consider this as an improvement, but we're not yet 100% about its timeline. Unlike Jackson, Gson doesn't support asynchronous parsing...

It's not clear at this point whether a limited encoder/decoder support for GSON would be still helpful to the Spring community. If anyone is interested in this feature, please comment...

Hi @chancekim - thanks for reaching out! This is pretty late in the 5.3.x generation and we're working on the upcoming 6.0.x. Introducing a new feature in 5.3.x at this...

@JevgenijZubovskij-UnlikelyAI this feature is not implemented and it's in the 6.X Backlog right now. We only got one person interested so far and we never got feedback on the limitations...

@shanewow would the limitations listed in https://github.com/spring-projects/spring-framework/issues/27131#issuecomment-874160517 be acceptable for your use case?

@encircled thanks for the offer but I think I already have the change ready. I never pushed it because I never got any answer from interested parties about the limitation...

Besides the exception hierarchy (something to be looked at in Spring Security), I think this shows the expected behavior. The trace Id is available within the scope of the observation...

Hi @emaarco , thanks for this detailed report. I think we already allow the `GraphQlTester` to resolve documents and fragments against several locations. You can configure a custom `documentSource` on...

Sorry I missed your previous comment. Let's add a code snippet in https://docs.spring.io/spring-graphql/reference/testing.html#testing.graphqltester.builder

Closing in favor of #1285