apache / apache/grails-intellij-plugin
Supply Javadoc annotation to specify i18n lookup for Grails tag libraries
- Dominant language
- Java
- Stars
- 17
- Forks
- 4
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
Using the build-in grails message taglib - <g:message code="" /> - within the "code" parameter, intellij can autocomplete from i18n property-files.
If using a custom tag library to lookup i18n keys, intellij should supply an annotation to mark the paramater as a i18n property to enable auto completion in custom tags.
Issue reported here: [http://devnet.jetbrains.com/message/5498078](http://devnet.jetbrains.com/message/5498078)
Mail from <hidden-personal-data>:
It's not possible right now. Please file a feature request at [http://youtrack.jetbrains.com/issues/IDEA](http://youtrack.jetbrains.com/issues/IDEA) and we'll consider adding this feature.
We could add a special JavaDoc tag that will be used to determine that the parameter should be completed as i18n property.
---
*Imported from [IDEA-113409](https://youtrack.jetbrains.com/issue/IDEA-113409) · 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 built-in Grails message tag library and the custom tag-library parameter described in the issue, then review how IntelliJ recognizes i18n keys in the g:message code parameter. Done means a documented Javadoc annotation can mark a custom tag parameter so IntelliJ offers autocomplete from i18n property files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100