The GitHub Actions job "Code Style" on grails-core.git/feature/gsp-escaped-dollar-8.0.x has succeeded. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: daaa4048b0e78e84418cb9493bbff8ea0eb18324 / Scott Murphy Heiberg <[email protected]> Support escaping a GSP expression with a backslash \${...} in template text now renders a literal ${...} instead of being evaluated: the scanner leaves the escaped sequence in the surrounding HTML token and the parser drops the backslash when writing it out. Escaping is resolved at parse time, before code generation, so all compilation modes behave identically and escaped text is invisible to static compilation. The primary use is JavaScript template literals, whose interpolation placeholders share the ${...} syntax. Only the backslash performing the escape is removed, each expression must be escaped individually, and expressions in tag attributes cannot be escaped this way. Also adds the junit-jupiter-engine test runtime dependency that grails-gsp-core was missing: the module declared only the Jupiter API, so the JUnit Platform silently skipped its Jupiter test classes, including all of GroovyPagesTemplateEngineTests. Claude-Session: https://claude.ai/code/session_01WtCxMe9pfmy7tiHCUr5THN Report URL: https://github.com/apache/grails-core/actions/runs/31655539868 With regards, GitHub Actions via GitBox
