The GitHub Actions job "SiteMesh 2 Compatibility" on grails-core.git/fix/resource-link-controller-lookup has succeeded. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: f49e676d6f063e2b16e6e6b3e185ef8e842c796a / Scott Murphy Heiberg <[email protected]> Resolve the controller for an uninitialised association too An association rendered while still a lazy proxy took a different path from one already loaded: AbstractLinkingRenderer passes the instance when initialised, but the domain class name when it is a proxy, to avoid loading it. Only the instance path resolved the controller, so the same association rendered /authors/2 or /author/2 depending on the session's fetch state. A domain class passed to the resource attribute now resolves through the same rule as an instance, and the renderer passes the associated entity's class rather than its decapitalised name. Both paths agree, and the class form keeps the naming convention precedence, so it is additive on the same terms. A string passed to the resource attribute is still treated as a literal controller name, since it cannot be distinguished from one. Report URL: https://github.com/apache/grails-core/actions/runs/33285177843 With regards, GitHub Actions via GitBox
