The GitHub Actions job "CI - Groovy Joint Validation Build" on 
grails-core.git/fix/config-export-bracketed-key-7.0.x has failed.
Run started by GitHub user codeconsole (triggered by codeconsole).

Head commit for run:
1b27bef89ff94bb25834b677da3ae4ca9727f6bb / Scott Murphy Heiberg 
<[email protected]>
Skip a dotted name only when its bracketed key exports its value

At the root, the walk skipped a flat key such as app.routes.k whenever
a bracketed key, app.routes[k], named it. A put of the dotted key after
the bracketed one writes only that flat key, so after
merge(['app.routes[k]': 'old'], true) and put('app.routes.k', 'new')
the walk skipped the flat key holding 'new', the nested entry was
skipped as exported by app.routes[k], and nothing exported 'new', where
7.0.x exported app.routes.k=new.

The walk now skips a flat key of the map only when the bracketed key
exports the same value, and skips a nested entry only when, besides its
bracketed key exporting it, the walked map holds no flat key under the
entry's dotted name with another value. Where the dotted names and the
bracketed key disagree, both are exported, as on 7.0.x, and the value
written last is the one exported under the dotted name: 'new' for the
put above, and also for merge(['app.routes.k': 'old'], true) followed
by merge(['app.routes[k]': 'new'], true), where the flat key
app.routes.k keeps 'old'. Where they agree, as for a map from
application.yml, the entry is still exported once, in brackets.

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

With regards,
GitHub Actions via GitBox

Reply via email to