borinquenkid opened a new pull request, #16204:
URL: https://github.com/apache/grails-core/pull/16204

   ## Summary
   Stacked on #16201. Fixes a series of IntelliJ-flagged issues in 
`org.grails.gorm.graphql.types.*`:
   - `DateCoercion`: fixed an NPE when no date formats are configured.
   - `AbstractObjectTypeBuilder`: fixed a control-flow issue where `build()`'s 
declared-then-reassigned `objectType` local confused Groovy's static type 
checker on `objectTypeCache.put(...)`; fixed an unrelated latent bug where an 
`ArrayList` capacity was computed from a not-yet-declared `properties` variable 
(which actually resolved to the unrelated `GroovyObject#getProperties()` bean 
map); removed an unused parameter from `buildInterfaceType`; and migrated the 
deprecated `GraphQLInterfaceType.Builder#typeResolver` call to registration via 
`GraphQLCodeRegistry.Builder`. Added the first direct coverage of the 
interface-type branch (a root entity with child entities), which no other spec 
reached.
   - All `Coercing` implementations in `types.scalars.coercing`: migrated off 
the deprecated 1-arg `serialize`/`parseValue`/`parseLiteral` overrides to the 
context/locale-aware overloads, fixing a `ClassCastException`-in-waiting in 
`ByteArrayCoercion#parseLiteral`, a deprecated `Character` constructor usage in 
`CharacterArrayCoercion`, and an unassigned-variable branch in 
`InstantCoercion#parseLiteral` along the way.
   
   ## Test plan
   - [x] `./gradlew :grails-data-graphql-core:test :grails-data-graphql:test 
:grails-data-graphql-core:codeStyle :grails-data-graphql:codeStyle` passes, 
including `SchemaSpec` which exercises these coercions through real GraphQL 
query execution
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]

Reply via email to