[JBoss JIRA] (ERT-52) Need to add Launch Configuration for gulp [EBZ#486232]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-52?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-52:
----------------------------
Sprint: devex #115 May 2016
> Need to add Launch Configuration for gulp [EBZ#486232]
> ------------------------------------------------------
>
> Key: ERT-52
> URL: https://issues.jboss.org/browse/ERT-52
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Labels: 3.8_M6, General, bzira
> Fix For: Neon (4.6) M6
>
> Original Estimate: 1 day, 7 hours
> Remaining Estimate: 1 day, 7 hours
>
> Gulp support should have not only Launch Shortcut but also a separate Lauch Configuration / Launch Config Type for task invocations. The main improvements are:
> - Ability to configure tasks
> - Tasks will be added to Launch Bar
> LC should be placed under org.eclipse.ui.externaltools the same as Ant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-53) Need to add Launch Configuration for grunt [EBZ#486233]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-53?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-53:
----------------------------
Sprint: devex #115 May 2016
> Need to add Launch Configuration for grunt [EBZ#486233]
> -------------------------------------------------------
>
> Key: ERT-53
> URL: https://issues.jboss.org/browse/ERT-53
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Labels: 3.8_M6, General, bzira
> Fix For: Neon (4.6) M6
>
> Original Estimate: 1 day, 7 hours
> Remaining Estimate: 1 day, 7 hours
>
> Grunt support should have not only Launch Shortcut but also a separate Lauch Configuration / Launch Config Type for task invocations. The main improvements are:
> - Ability to configure tasks
> - Tasks will be added to Launch Bar
> LC should be placed under org.eclipse.ui.externaltools the same as Ant
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-62:
----------------------------
Sprint: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #113 April 2016 (was: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #113 April 2016, devex #115 May 2016)
> Refactor JSDT Code Completion [EBZ#486776]
> ------------------------------------------
>
> Key: ERT-62
> URL: https://issues.jboss.org/browse/ERT-62
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Ian Stewart-Binks
> Labels: General, bzira
>
> The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions.
> A proposal base for the code completion engine should include, but is not necessarily limited to:
> - Keywords
> - Identifiers (declared variables and functions in currently open JS file)
> - Recently used methods of functions (currently open JS file as a bare minimum)
> All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-212) Apply Completion & JSON Schema support for "enum" & "default" [EBZ#494100]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-212?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-212:
-----------------------------
Sprint: devex #115 May 2016
> Apply Completion & JSON Schema support for "enum" & "default" [EBZ#494100]
> --------------------------------------------------------------------------
>
> Key: ERT-212
> URL: https://issues.jboss.org/browse/ERT-212
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Priority: Trivial
> Labels: bzira, wst.json
>
> JSON Editor completion should support JSON Schema "enum" when completion is applied.
> Takes a samples with tsconfig.json which defines a JSON Schema for "target" like this:
> -----------------------------------------------
> "target": {
> "description": "Specify ECMAScript target version.",
> "enum": [
> "es3",
> "es5",
> "es6",
> "es2015"
> ],
> "default": "es3"
> }
> -----------------------------------------------
> When I open completion, it shows "target", and when I apply the completion, it generates only
> -----------------------------------------------
> "target"
> -----------------------------------------------
> It should be very cool, if apply completion:
> * generates
> -----------------------------------------------
> "target": "es3"
> -----------------------------------------------
> because "es3" is defined as "default".
> * and when I do tab on "es3" value, it shows a second completion popup with enum values ("es3", "es5", etc)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months