Add support TraitInjector for GroovyPage#1591
Merged
rainboyan merged 3 commits intoJul 11, 2026
Merged
Conversation
Groovy Page now is a Artefact, just like Controller, Service, it can be transformed and injected when compiling
- GroovyPageInjector should only inject GroovyPage - Introduce GroovyPageTransform to support TraitInjector for GroovyPage - Use GrailsAwareInjectionOperation instead of GroovyPageInjectionOperation for GroovyPageClassLoader - Deprecated GroovyPageInjectionOperation in favor of GrailsAwareInjectionOperation
rainboyan
added
type: feature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce GroovyPageClass and GroovyPageArtefactHandler to make GSP as an Artefact, just like Controller, Service, it can be transformed and injected
Use GroovyPageTransform to support
TraitInjectorfor GroovyPage