apache / apache/grails-intellij-plugin

Convenience - Provide easy access to Config and BuildConfig for Grails active application

Open
#128 0 comments 0 reactions 0 assignees View on GitHub
enhancement imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

Requesting for a quick access button to edit Config and BuildConfig files, that are typically frequently used.

Using Favorites does not help this very much. When working with multiple grails projects (windows) at the same time, which has several
plugins, inplacePlugins, there can be only on Favorites area for all the windows. That means, I have to keep adding the Config and BuildConfig files everytime to all those windows (i may not have all of them open all the time).

Just like Intellij (very smartly) provides Controllers, Domains, Views buttons once I am in the editor, it would be nice to have permanent buttons (quick links) to Config and BuildConfig for the project currently in the editor. Because of Grails nature of plenty of modules and hierarchies, i feel a lot of time is spent on just navigating the left side tree (up and down and locating the right file, because many file names look same and it is not clear immediately which file belongs to which project or plugin). The Controller/Domain/Views/link to views alongside the methods largely reduce this navigation. Adding Config and BuildConfig to that will help a lot more too.

Thank you,

---

*Imported from [IDEA-108335](https://youtrack.jetbrains.com/issue/IDEA-108335) · 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 by locating the existing Controllers, Domains, and Views quick-link implementation in the Grails IntelliJ plugin, then trace how it identifies the project currently open in the editor. Determine where Config and BuildConfig links should appear and verify that they resolve to the corresponding project files without relying on shared Favorites.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.