[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny reassigned ERT-177:
-----------------------------------
Assignee: Victor Rubezhny
> Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
> ---------------------------------------------------------------------------------------------------
>
> Key: ERT-177
> URL: https://issues.jboss.org/browse/ERT-177
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: 3.8_RC1, General, bzira
> Fix For: Neon (4.6) RC3
>
>
> Created attachment 261462
> Selection related errors
> See the screenshot attached for illustration.
> Steps for reproduce:
> - Create a javascript file with a function and a call to that function.
> - Try to invoke content assist: FAIL: no new function appears in CA proposals
> - Save, close and open the file again.
> - Try to invoke content assist: Now the new function appears in CA proposals
> - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration
> - FAIL: See wrong text regions highlighted.
> - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-144) Gulp is not available in the Quick access [EBZ#492124]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-144?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-144:
-----------------------------
Sprint: devex #114 May 2016, devex #115 May 2016 (was: devex #114 May 2016)
> Gulp is not available in the Quick access [EBZ#492124]
> ------------------------------------------------------
>
> Key: ERT-144
> URL: https://issues.jboss.org/browse/ERT-144
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: General, bzira
>
> "Run as Gulp task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected:
> - IProject with gulpfile.js (launch default task from gulpfile.js)
> - IFile gulpfile.js (default task should be run)
> - ITask (run gulp task)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-145) Grunt is not available in the Quick access [EBZ#492125]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-145?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-145:
-----------------------------
Sprint: devex #114 May 2016, devex #115 May 2016 (was: devex #114 May 2016)
> Grunt is not available in the Quick access [EBZ#492125]
> -------------------------------------------------------
>
> Key: ERT-145
> URL: https://issues.jboss.org/browse/ERT-145
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: General, bzira
>
> "Run as Grunt task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected:
> - IProject with gruntfile.js (launch default task from gruntfile.js)
> - IFile gruntfile.js (default task should be run)
> - ITask (run grunt task)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny updated ERT-177:
--------------------------------
Fix Version/s: Neon (4.6) RC3
(was: Neon (4.6) RC1)
> Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
> ---------------------------------------------------------------------------------------------------
>
> Key: ERT-177
> URL: https://issues.jboss.org/browse/ERT-177
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: 3.8_RC1, General, bzira
> Fix For: Neon (4.6) RC3
>
>
> Created attachment 261462
> Selection related errors
> See the screenshot attached for illustration.
> Steps for reproduce:
> - Create a javascript file with a function and a call to that function.
> - Try to invoke content assist: FAIL: no new function appears in CA proposals
> - Save, close and open the file again.
> - Try to invoke content assist: Now the new function appears in CA proposals
> - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration
> - FAIL: See wrong text regions highlighted.
> - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-177:
-----------------------------
Sprint: devex #114 May 2016, devex #115 May 2016 (was: devex #114 May 2016)
> Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]
> ---------------------------------------------------------------------------------------------------
>
> Key: ERT-177
> URL: https://issues.jboss.org/browse/ERT-177
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: 3.8_RC1, General, bzira
> Fix For: Neon (4.6) RC1
>
>
> Created attachment 261462
> Selection related errors
> See the screenshot attached for illustration.
> Steps for reproduce:
> - Create a javascript file with a function and a call to that function.
> - Try to invoke content assist: FAIL: no new function appears in CA proposals
> - Save, close and open the file again.
> - Try to invoke content assist: Now the new function appears in CA proposals
> - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration
> - FAIL: See wrong text regions highlighted.
> - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted.
--
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 Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-212:
---------------------------------------
Summary: 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
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
[JBoss JIRA] (ERT-213) Support for JSON Schema Catalog [EBZ#494110]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-213:
---------------------------------------
Summary: Support for JSON Schema Catalog [EBZ#494110]
Key: ERT-213
URL: https://issues.jboss.org/browse/ERT-213
Project: Eclipse Release Train
Issue Type: Task
Components: WTP Source Editing
Reporter: Friendly Jira Robot
Priority: Trivial
JSON Schema store provides a JSON Schema catalog at https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catal...
My idea is to have the same thing than XML Catalog :
* System catalog where WTP JSON plugin host https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catal...
* User Catalog to defines your own catalog
When a JSON file is opened, it checks:
* if a JSON Schema exists coming from the existing plugin extension point org.eclipse.wst.json.core.schemaCatalogContributions
* if not, it uses System and User JSON catalog and download the well JSON Schema declared inside JSON Schema Catalog.
Takes samples:
1) User create a JSON file with name "package.json", the JSON Schema which is used comes from org.eclipse.wst.json.core.schemaCatalogContributions (because it exists)
2) User create a JSON file with name "babelrc.json". In this case, org.eclipse.wst.json.core.schemaCatalogContributions doesn't define it and http://json.schemastore.org/babelrc is downloaded, because it is declared like this:
-----------------------------------
"schemas": [
{
"name": "babelrc.json",
"description": "Babel configuration file",
"fileMatch": [ ".babelrc" ],
"url": "http://json.schemastore.org/babelrc"
},
-----------------------------------
inside the system JSON Schema catalog (see at
https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catal...)
It should be good too to give the capability to link a JSON Schema to an image to know which icon should be displayed for the JSON file in the "Project Explorer".
Please note that today it exists JSON Catalog (which is a copy/paste from XML Catalog) in the core. An UI JSON Catalog must be implemented to show system catalog and user catalog (like XML Catalog).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months