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/23 22:33:18 UTC
[GH] (grails-core/perf/config-lookup-9.0.x): Workflow run "Groovy Snapshot Canary Build" is working again!
The GitHub Actions job "Groovy Snapshot Canary Build" on grails-core.git/perf/config-lookup-9.0.x has succeeded.
Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run:
553eafbbf67d9cf6115c24c15ef78e2621f02d02 / Scott Murphy Heiberg <sc...@alwaysvip.com>
Write the flat alias of a block a nested dotted merge creates at the root
navigateSubMap wrote the alias of each block it created relative to the
map it was called on, so for a dotted key inside a nested map, such as
x: ['a.b': 'new'], the alias landed inside the x sub-map and the root
alias x.a kept the scalar an earlier merge had left there. getProperty
read that scalar first while navigate returned the block.
The alias is now written at the configuration root under the block's
full path, whichever map the walk started on, and a scalar there is
replaced as it is when the block is merged at the root. A sub-map no
longer carries a relative alias for an intermediate block, which only
this path ever wrote. The same path serves a dot-notation write below
an existing block, config.x.a.b = value, which now leaves the root
alias x.a as a merge does; GrailsConfigSpec pinned the missing alias
and expects it now, as its map-syntax sibling already did.
Report URL: https://github.com/apache/grails-core/actions/runs/40013958549
With regards,
GitHub Actions via GitBox