[
https://issues.jboss.org/browse/JBIDE-14333?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-14333:
---------------------------------------
I can add the org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet
command.
However, the cheatsheet author has to take into account the command and ensure it is
called (required).
Do you agree me to do the following:
- add the org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet command that
will return the current project as the result
The $\{currentProject\} syntax will work automatically
- leave the current replacement that doesn't require adding a command
have context sensitive parameterized commands for open file, show
type etc. with proper API
-------------------------------------------------------------------------------------------
Key: JBIDE-14333
URL:
https://issues.jboss.org/browse/JBIDE-14333
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: project-examples
Reporter: Max Rydahl Andersen
Fix For: 4.1.0.Beta1, 4.1.0.Beta2
currently our custom cheatsheet commands requires the project name(s) to be known
upfront. We should make them less reliant on project names and if at all possible have the
project name calculated based on the project the cheatsheet file is open in.
The commands should also actually be commands with named parameters so the order of
parameters does not matter and we should make sure these have a good and long term API so
cheatsheets will continue to work well in the future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira