[JBoss JIRA] (ERT-386) code formatter inserts line breaks after const qualifier [EBZ#399501]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-386?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-386:
----------------------------
Story Points: 1 (was: 10)
> code formatter inserts line breaks after const qualifier [EBZ#399501]
> ---------------------------------------------------------------------
>
> Key: ERT-386
> URL: https://issues.jboss.org/browse/ERT-386
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Angel Misevski
> Priority: Trivial
> Labels: General, bzira
>
> for a code line like
> const FOO = "bar";
> the code formatter inserts a line break after the const keyword, resulting in
> const
> FOO = "bar";
> While this simply looks ugly (to me) code verification reports a warning "Missing semicolon", so I get many nasty m,arkers on source files.
> Please remove those line breaks or make them settable in the formatter settings.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-379) Exceptions while expanding Variables view [EBZ#499600]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-379?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-379:
----------------------------
Sprint: (was: devex #119 August 2016)
> Exceptions while expanding Variables view [EBZ#499600]
> ------------------------------------------------------
>
> Key: ERT-379
> URL: https://issues.jboss.org/browse/ERT-379
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Labels: 3.8.1, Debug, bzira
> Fix For: Neon.1 (4.6)
>
>
> Steps to reproduce:
> -------------------
> 1) import: https://github.com/ibuziuk/myRESTApp
> 2) server.js -> Debug As -> Node.js Application
> 3) Expand various items variables view.
> Stack trace:
> ================================================
> org.eclipse.wst.jsdt.chromium.internal.protocolparser.implutil.CommonImpl$ParseRuntimeException: On demand parsing failed for {"ref":118,"propertyType":2,"attributes":7}
> at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.handle(DynamicParserImpl.java:696)
> at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.JsonInvocationHandler.invoke(JsonInvocationHandler.java:35)
> at com.sun.proxy.$Proxy88.name(Unknown Source)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil$PropertyNameGetter$SubpropertyNameGetter.getName(V8ProtocolUtil.java:216)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil$PropertyNameGetter$SubpropertyNameGetter.getName(V8ProtocolUtil.java:1)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil.extractProperty(V8ProtocolUtil.java:150)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil.putMirror(V8ProtocolUtil.java:134)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.V8ProtocolUtil.extractObjectProperties(V8ProtocolUtil.java:94)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.SubpropertiesMirror$JsonBased.getProperties(SubpropertiesMirror.java:69)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase$1.runSync(JsObjectBase.java:176)
> at org.eclipse.wst.jsdt.chromium.util.AsyncFuture$SyncOperation.execute(AsyncFuture.java:171)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase.startPropertyLoadOperation(JsObjectBase.java:199)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase.getPropertyData(JsObjectBase.java:138)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsObjectBase.getBasicPropertyData(JsObjectBase.java:159)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getAdditionalPropertyData(JsFunctionImpl.java:82)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getVariableScopes(JsFunctionImpl.java:47)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.access$2(JsFunctionImpl.java:46)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl$1.getScopes(JsFunctionImpl.java:127)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateFunctionScopesVariable(Value.java:95)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateVariables(Value.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.ValueBase$ValueWithLazyVariables.getVariables(ValueBase.java:77)
> at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getValueChildren(VariableContentProvider.java:170)
> at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getAllChildren(VariableContentProvider.java:87)
> at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getChildCount(VariableContentProvider.java:49)
> at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.retrieveChildCount(ElementContentProvider.java:118)
> at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$2.run(ElementContentProvider.java:67)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.wst.jsdt.chromium.internal.protocolparser.JsonProtocolParseException: Field is not optional: name (in type org.eclipse.wst.jsdt.chromium.internal.v8native.protocol.input.data.PropertyObject)
> at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.parse(DynamicParserImpl.java:729)
> at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.parse(DynamicParserImpl.java:715)
> at org.eclipse.wst.jsdt.chromium.internal.protocolparser.dynamicimpl.DynamicParserImpl$LazyParseFieldMethodHandler.handle(DynamicParserImpl.java:694)
> ... 26 more
> ================================================
> java.lang.NullPointerException
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getAdditionalPropertyData(JsFunctionImpl.java:82)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.getVariableScopes(JsFunctionImpl.java:47)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl.access$2(JsFunctionImpl.java:46)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.value.JsFunctionImpl$1.getScopes(JsFunctionImpl.java:127)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateFunctionScopesVariable(Value.java:95)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.Value.calculateVariables(Value.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.ValueBase$ValueWithLazyVariables.getVariables(ValueBase.java:77)
> at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getValueChildren(VariableContentProvider.java:170)
> at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getAllChildren(VariableContentProvider.java:87)
> at org.eclipse.debug.internal.ui.model.elements.VariableContentProvider.getChildren(VariableContentProvider.java:57)
> at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.retrieveChildren(ElementContentProvider.java:91)
> at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$1.run(ElementContentProvider.java:44)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-383) JSONEditor: NPE when working with an array of objects [EBZ#497261]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-383?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-383:
----------------------------
Sprint: devex #120 September 2016 (was: devex #119 August 2016)
> JSONEditor: NPE when working with an array of objects [EBZ#497261]
> ------------------------------------------------------------------
>
> Key: ERT-383
> URL: https://issues.jboss.org/browse/ERT-383
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Snjezana Peco
> Labels: bzira, wst.json
>
> I have not been able to reproduce this consistently, but here it goes:
> Create a JSON file with following content:
> {
> "thirdaddition": true,
> "name": "JSONEditorTest2",
> "secondaddition": 2,
> "description": "JSONEditorTest description2",
> "version": "1.0.1",
> "main": "app.js",
> "scripts": {
> "start": "node app.js"
> },
> "array_of_objects": [{"abc": 1234}, {"value": 1234 }]]}}}}}}]}],
> "value": "test",
> "anothervalue": "1234"
> }
> When adding and removing (invalid) closing brackets, then modifying the value of the second array element (value), I tend to see this exception:
> java.lang.NullPointerException
> at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeAttrValue(JSONModelParser.java:89)
> at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeRegion(JSONModelParser.java:131)
> at org.eclipse.wst.json.core.internal.document.JSONModelImpl.regionChanged(JSONModelImpl.java:654)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:542)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1180)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144)
> at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149)
> at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106)
> at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:103)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1094)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1119)
> at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:625)
> at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:233)
> at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7374)
> at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8225)
> at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2334)
> at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7164)
> at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:6022)
> at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:6049)
> at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5733)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1538)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1534)
> at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:515)
> at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1090)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5817)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68)
> at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:610)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5727)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5789)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5218)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-214) Validate JSON file with JSON Schema [EBZ#494111]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-214?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-214:
----------------------------
Sprint: devex #116 June 2016, devex #118 July 2016, devex #120 September 2016 (was: devex #116 June 2016, devex #118 July 2016, devex #119 August 2016)
> Validate JSON file with JSON Schema [EBZ#494111]
> ------------------------------------------------
>
> Key: ERT-214
> URL: https://issues.jboss.org/browse/ERT-214
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Snjezana Peco
> Priority: Trivial
> Labels: bzira, wst.json
> Fix For: Neon.1 (4.6)
>
>
> It's a very big task, but it should be fantastic if WTP Validator could validate JSON file by using JSON Schema.
> To do that:
> * JSONSchemaDocument should support the full specification of JSON Schema.
> * minimal-json should be improved to collect line, column or perhaps we could use IJSONDocument to validate it with JSON Schema.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-387) JSON editor "supports" comments, not supported by JSON [EBZ#499705]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-387?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-387:
----------------------------
Sprint: devex #120 September 2016 (was: devex #119 August 2016)
> JSON editor "supports" comments, not supported by JSON [EBZ#499705]
> -------------------------------------------------------------------
>
> Key: ERT-387
> URL: https://issues.jboss.org/browse/ERT-387
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Snjezana Peco
> Priority: Trivial
> Labels: bzira, wst.json
>
> I tried commenting a line in a JSON file using the common syntax "/* comment */":
> /*"jquery/jquery-min": "1.12",*/
> This caused the line to become blue, so I figured JSON must support comments. But as mentioned in https://en.wikipedia.org/w/index.php?title=JSON&oldid=734431215 this is not the case.
> Ticket #495578 explains that Angelo ZERR decided to support "JSON comments" since .jshintrc (no idea what that is) uses it. In my opinion, this should be disabled by default, but for sure, it should be possible to disable. Currently, all JSON highlights are mandatory (the checkboxes are disabled).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-346) If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-346?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-346:
----------------------------
Sprint: (was: devex #119 August 2016)
> If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703]
> --------------------------------------------------------------------------------------------------
>
> Key: ERT-346
> URL: https://issues.jboss.org/browse/ERT-346
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
>
> We use feature in node that we can put out modules in a “node_modules” in a parent folder and it will be properly found: https://nodejs.org/api/modules.html#modules_loading_from_node_modules_fol...
> Node is working properly but if I add a breakpoint in a source file inside “node_modules” the breakpoint does not get hit.
> To reproduce the issue:
> 1. Create a JavaScript project “test”.
> 2. Add a file “test.js” to the project with content:
> var m1 = require("m1");
> console.log("m1.myFunc = " + m1.myFunc(3));
> 3. Create a JavaScript project called “node_modules”.
> 4. Add a folder “m1” to the project “node_modules”.
> 5. Add a file “index.js” to the folder “m1” with content:
> module.exports.myFunc = function( i) {
> return i*i;
> }
> 6. Debug “test.js” as Node – it works. Node is finding property “index.js”. 7. Add a breakpoint to “index.js”.
> 8. Debug “test.js” as Node – it runs, but the breakpoint does not suspend the target.
> Is there workaround for this issues?
> Most of our projects are relying on the “node_modules” being found in the parent folder. That is making most of our code hard to debug.
> I tested this on Ubuntu 14.04.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months