Allow defining localeResolver in Configuration #12471
Closed
Conversation
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
Define localResolver and localeChangeInterceptor bean in Configuration inplace of the Plugin
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.
Currently custom localeResolver only allow defining beans in
resources.groovy, I think custom localeResolver and localeChangeInterceptor beans could be defined inConfiguration, this will be benefit from Spring Boot@EnableAutoConfigurationwith spring-boot-starters.The priority order of loading
Beanis,GrailsPlugin > Configuration > resources.groovy
So, this PR will not change the default Grails way.