apache / apache/grails-intellij-plugin
Grails: user defined config properties could be resolved and suggested by completion in controllers
- Dominant language
- Java
- Stars
- 17
- Forks
- 4
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
Provide a Grails application module.
Provide grails-app/conf/Config.groovy with user defined properties like:
```
environments {
ideatest {
my.own.secret = "Secret property string."
}
}
my.own.secret2 = "Secret property string 2."
```
Provide a reference to them in grails-app/controllers/AnyController:
```
def sample = {
render "
$ConfigurationHolder.config.my.own.secret
"render "
$ConfigurationHolder.config.my.own.secret2
"}
```
Try completion after "$ConfigurationHolder.config.": they suggest predefined Grails properties like "grails.views.gsp.encoding", but not user defined properties.
108.578.
---
*Imported from [IDEA-71624](https://youtrack.jetbrains.com/issue/IDEA-71624) · Type: Feature · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the grails-app/conf/Config.groovy example and the grails-app/controllers/AnyController reference, then reproduce completion after "$ConfigurationHolder.config.". Trace how predefined Grails properties are suggested and make user-defined properties available there; done means both sample properties appear in completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100