apache / apache/grails-intellij-plugin
Do not offer to create a controller/domain
- Dominant language
- Java
- Stars
- 17
- Forks
- 4
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
See attach. I think it's counterproductive to offer to create a controller/domain instead of simple Groovy class. I'm not even mention that it's very slow (and requires that the project is compiled)!
---
*Imported from [IDEA-112909](https://youtrack.jetbrains.com/issue/IDEA-112909) · Type: Usability Problem · 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
No source file, test, or attachment is included in the issue. Start by locating the IntelliJ action or dialog that offers to create a controller/domain, then trace how it presents the simple Groovy class alternative. Done means the unnecessary controller/domain offer is removed or replaced as described, with the behavior verified in the relevant plugin test or manually in IntelliJ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100