Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Please add your own entries, and increment the vote count for features that interest you.  IMPORTANT: Please try and consider your suggestions from an IntelliJ design and terminology viewpoint rather than trying to insert ideas that are concepts from other IDEs that don't make sense in the IDEA world.

Debugging

  • Full debugging support, including setting breakpoints, watch variables, view stack, view vars in scope, etc.
  • Support for transitioning from Java to Groovy and vice versa. 
  • Ability to filter stack traces to show only Groovy classes. 
  • Ability to debug scripts in addition to classes.
  • Allow Alt-F8 to evaluate Groovy expressions

Editing

  • Code Formatting (as currently supported for Java code)
  • Auto insertion of packages and imports (as currently supported for Java code
  • Code Completion (including support for Builders)
  • Intentions support
  • Syntax Highlighting (including the ability to color Groovy specific constructs differently) 

Execution & Testing 

  • Ability to run Groovy based tests in a similar fashion to standard JUnit tests, with matching green/red runner results view.
  • The ability to specify Groovy Run/Debug configurations for scripts and classes.  (Scripts shows in the current editor should not require the developer to setup a run/debug config and should be executable via the standard shift-F10/F9 hotkeys.)
  • Gant integration (from an editing perspective this is covered by builder support but it would be nice to have a Gant tab just like there is an Ant tab in IDEA).
  • Allow starting the GroovyConsole with the current project's classpath being available
  • Groovy scratchpad (interactive execution of Groovy code like in the GroovyConsole but with Idea's editor support)

Grails

Currently, Grails suggestions are being collected in a non-IDE specific location.

Misc

  • Groovy classes should appear in the "Go To Class" dialogue (CTRL-N).  Groovy classes in the list should be discernible from Java classes by a unique icon.
  • Other "Go To" support like Java code, eg, CTRL-B or CTRL-click to jump to a class definition
  • Find All References
  • Type Hierarchy
  • Groovy Search
  • Show javadoc
  • Ability to specify Groovy specific code style
  • Cross compiler allowing to reference Groovy classes from Java and Java classes from Groovy 
  • Per-directory control over which Groovy source trees should be compiled and which should not; this is especially important for Grails where compiling the Groovy code under project/grails-app can interfere with the application, wheres the code under src/groovy is compiled
  • The ability to register Groovy SDKs just like you can with Java so you can keep different versions of Groovy available for testing at the same time and be able to easily switch between them. 
  • When creating any new class/controller/domain/gsp/script/template check to see if the project is using version control and ask the user if they would like to add it.

Refactoring

  • Rename/move class
  • Rename method/variables
  • Extract Method
  • Extract Variable
  • Inline method/variable
  • New Groovy Refactoring: extract conditional to closure
    becomes
  • New Groovy Refactoring: extract local closure
    becomes

Templating 

  • Live Templates support
  • No labels