You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/10/21 13:35:40 UTC

[GH] (grails-core/fix/16675-map-entries-named-like-properties): Workflow run "Code Style" failed!

The GitHub Actions job "Code Style" on grails-core.git/fix/16675-map-entries-named-like-properties has failed.
Run started by GitHub user jdaugherty (triggered by jdaugherty).

Head commit for run:
03fe486da61c6f29b33dcb22fa74953cc66cb1d4 / James Daugherty <jd...@jdresources.net>
Scope the loaded-map wrapper note to GORM for MongoDB

The upgrade note described the dirty-checking wrapper as what every
loaded GORM Map property comes back as. That is true of GORM for
MongoDB only. With GORM for Hibernate a loaded Map property is
Hibernate's PersistentMap, whose own accessors (key, value, owner, role,
size, session, dirty, ...) hide entries of those names on Groovy 5 and
are not redirected, so the note now says so and points at get.

The metaClass sentence presented the subscript write as a Groovy 5
change. On Groovy 4 the write already set the metaclass of the map and
threw GroovyCastException for any other value; only the read changed.

The MongoDB spec now asserts that the loaded map is a DirtyCheckingMap
before it reads the entries named like the wrapper's accessors, so the
block keeps exercising the getProperty/setProperty override rather than
passing against a plain map.

Report URL: https://github.com/apache/grails-core/actions/runs/39606215420

With regards,
GitHub Actions via GitBox