The GitHub Actions job "Code Style" on grails-core.git/fix/null-constructor-arg-groovy4 has succeeded. Run started by GitHub user davydotcom (triggered by davydotcom).
Head commit for run: cc919dca2c6127d9df8aa54e2e6599659772355a / David Estes <[email protected]> fix: handle null argument in GORM domain class constructor (Groovy 4 regression) In Groovy 3, calling new DomainClass(null) was resolved by the runtime to the implicit map-based constructor and treated equivalently to new DomainClass(). Groovy 4 changed how constructor resolution works at runtime and no longer matches a null argument to the implicit map constructor, resulting in: GroovyRuntimeException: Could not find matching constructor for: DomainClass(null) This commit injects an explicit Map constructor into GORM entity classes via GormEntityTransformation. The constructor handles null gracefully by skipping property assignment, making it behave identically to the no-arg constructor. A corresponding no-arg constructor is also ensured since adding any explicit constructor prevents Groovy from auto-generating the default one. Co-Authored-By: Oz <[email protected]> Report URL: https://github.com/apache/grails-core/actions/runs/22631844876 With regards, GitHub Actions via GitBox
