[JBoss JIRA] (ERT-338) [formatter] Unwanted alignment on Enter when inside array literal [EBZ#356606]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-338?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-338:
----------------------------
Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016)
> [formatter] Unwanted alignment on Enter when inside array literal [EBZ#356606]
> ------------------------------------------------------------------------------
>
> Key: ERT-338
> URL: https://issues.jboss.org/browse/ERT-338
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Shane Bryzak
> Labels: Future, General, bzira
> Fix For: Neon.1 (4.6)
>
>
> Eclipse 3.7 (I20110613-1736)
> JSDT 1.3.0 (20110527214303)
> WTP 3.3.0 (20100921193530)
> 1. Create a new JavaScript file and add this code:
> function() {
> var myArray = [];
> }
> 2. Put the editing caret between the square brackets, and press Enter.
> 3. You get
> function() {
> var myArray = [
> ];
> }
> Inside array literals, pressing Enter causes the editor to insert spaces to align the new line with the opening [ bracket. I expected it to just increase the indentation level.
> This happens when using a new workspace with all the default preference settings.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-339) Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-339?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-339:
----------------------------
Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016)
> Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931]
> -----------------------------------------------------------------------------
>
> Key: ERT-339
> URL: https://issues.jboss.org/browse/ERT-339
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Shane Bryzak
> Labels: General, bzira
> Fix For: Neon.1 (4.6)
>
>
> If you are writing an array initializer in JavaScript, you most likely want to it to look like this:
> var myArray = [
> item1,
> item2,
> item3,
> ...
> ];
> However, no matter how you configure Eclipse to format array initializers, it ignores it all and instead tries to make you kill yourself with frustration.
> Actually *typing* an array initializer goes like this, cursor position indicated by _
> 1. You type the following:
> var myArray = [_
> 2. Eclipse inserts a closing paren:
> var myArray = [_]
> 3. You press enter, expecting to a get a newline, but instead Eclipse interprets it as "move the cursor to the end of the line:
> var myArray = []_
> 4. You left-arrow the cursor back a position, and press enter again. This time, Eclipse does insert a newline. But it auto-indents as follows:
> var myArray = [
> _]
> Rather than following the same, sane behaviour it provides for object initializers, Eclipse idents the following line to the same column as the opening paren, it idents using spaces, even if you've configured it to use tabs and only tabs for indentation, and it leaves the closing paren on the same line, rather than moving it to the start of the next.
> Trying to fix the indentation is impossible, because it has used spaces instead of tabs. If you delete the spaces and press tab, it merely re-inserts the spaces and re-indents back to the column of the open paren!
> It's hard to adequately emphasise what a frustrating, poisonous impression this makes on someone using Eclipse as a tool for JavaScript development. It feels actively user-hostile.
--
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: 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
[JBoss JIRA] (ERT-221) Exception when debugging with chromium [EBZ#494731]
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/ERT-221?page=com.atlassian.jira.plugin.sy... ]
Ilya Buziuk updated ERT-221:
----------------------------
Sprint: devex #116 June 2016, devex #118 July 2016, devex #119 August 2016 (was: devex #116 June 2016, devex #118 July 2016)
> Exception when debugging with chromium [EBZ#494731]
> ---------------------------------------------------
>
> Key: ERT-221
> URL: https://issues.jboss.org/browse/ERT-221
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: 3.8_RC3, Debug, bzira
> Fix For: Neon (4.6) RC3
>
>
> Using EPP JavaScript RC2 package, using "Debug As > Node.js application" on some random file.
> This error seems to happen whenever the program is interrupted, for example because a dependency doesn't compile or whatever.
> Such remote interruption can happen pretty often, the shouldn't be treated as IDE error, but rather caught and presented to the user. Currently, it's logged in the IDE, and AERI suggests to open a ticket for that despite there is nothing wrong in the IDE. This gives an impression that debugger has bugs and this is going to flood AERI with no fair reason.
> --
> eclipse.buildId=4.6.0.I20160519-1730
> java.version=1.8.0_77
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.javascript.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.javascript.product
> org.eclipse.wst.jsdt.chromium.debug.core
> Error
> Fri May 27 11:23:55 CEST 2016
> SDK:org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection: Exception in message listener
> java.lang.IllegalStateException: Connection not attached
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.checkAttached(SocketConnection.java:455)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.send(SocketConnection.java:416)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$V8CommandOutputImpl.send(StandaloneVmImpl.java:249)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:133)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:1)
> at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.send(BaseCommandProcessor.java:75)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.sendV8CommandAsync(V8CommandProcessor.java:84)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.DebugSession.sendMessageAsync(DebugSession.java:101)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.processor.AfterCompileProcessor.messageReceived(AfterCompileProcessor.java:44)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.DefaultResponseHandler.handleResponseWithHandler(DefaultResponseHandler.java:60)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:145)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:1)
> at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:112)
> at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:115)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:116)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:122)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:211)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-143) Outline view is not refreshed properly when adding objects or array's children [EBZ#491928]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-143?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny reassigned ERT-143:
-----------------------------------
Assignee: Victor Rubezhny
> Outline view is not refreshed properly when adding objects or array's children [EBZ#491928]
> -------------------------------------------------------------------------------------------
>
> Key: ERT-143
> URL: https://issues.jboss.org/browse/ERT-143
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: bzira, wst.json
>
> When adding children to the JSON parent object the outline view is refreshed correctly, but when you add an array or an object to the parent Object and after that start adding children to that array or object the outline view is not properly refreshed all the times.
> Issue: The node of the array or object with children in the outline view is collapsed, if you keep adding more children with that node collapsed and then expand the node you can see the children displayed correctly, but if you expand the node before adding the new children, the new node doesn't appear in the outline view until you refresh the outline view manually or adding a new children and the parent is collapsed again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-143) Outline view is not refreshed properly when adding objects or array's children [EBZ#491928]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-143?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny resolved ERT-143.
---------------------------------
Resolution: Done
> Outline view is not refreshed properly when adding objects or array's children [EBZ#491928]
> -------------------------------------------------------------------------------------------
>
> Key: ERT-143
> URL: https://issues.jboss.org/browse/ERT-143
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Assignee: Victor Rubezhny
> Labels: bzira, wst.json
>
> When adding children to the JSON parent object the outline view is refreshed correctly, but when you add an array or an object to the parent Object and after that start adding children to that array or object the outline view is not properly refreshed all the times.
> Issue: The node of the array or object with children in the outline view is collapsed, if you keep adding more children with that node collapsed and then expand the node you can see the children displayed correctly, but if you expand the node before adding the new children, the new node doesn't appear in the outline view until you refresh the outline view manually or adding a new children and the parent is collapsed again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months