apache / apache/grails-intellij-plugin

Domain class dependencies diagram is shown for each domain class, rather than for the entire Grails module.

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

Description

To view domain class dependencies for a Grails module, you have to open any domain class in the editor, and click the "domain class dependencies" tab. So doing, each domain class shows a diagram, though in fact there is only one diagram that shows domain classes, dependencies and relationships across the entire Grails module.
It seems more logical to invoke domain class dependencies diagram from the context menu of the Domain Classes node or a domain class in the Grails tool window (same way as it is done, for example, in the Persistence tool window, where ER digram is invoked from the context menu of a persistence unit or entity.)

---

*Imported from [IDEA-51398](https://youtrack.jetbrains.com/issue/IDEA-51398) · 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

Start in the Grails tool window at the Domain Classes node and its domain-class context actions; compare how the Persistence tool window invokes an ER diagram from a persistence unit or entity. Trace the existing domain class dependencies tab and determine how one module-wide diagram can be opened from the node or a class. Done means the diagram is invoked from those context menus rather than separately per domain class.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.