@WebStormIDE i think the IDE skips flagging named imports as unused when inside `const {a,b} = require(…);`
-
-
Replying to @jasonmulligan
Can you please provide a screenshot showing that and a full code sample?
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
Named import assigned to const with a commonjs require
1 reply 0 retweets 0 likes -
Replying to @jasonmulligan
We couldn't reproduce the problem so a code sample or a screenshot would be helpful.pic.twitter.com/hjXA6thp1p
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
odd, i can reproduce on mac & windows... e.g. in this screenshot i added 'parse' & waited but no color change or squiggle... and it's this file https://github.com/avoidwork/tiny-translator/blob/master/lib/translator.js …pic.twitter.com/gjABWA3pFH
2 replies 0 retweets 0 likes -
Replying to @jasonmulligan
Can you please enable coding assistance for Node.js by pressing Alt-Enter on 'ulr' or 'path': that way the imported symbols will be properly resolved and the correct usages will be found.
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
that regressed with the latest stable version... ide flips back to ecma 5.1 when opening projects which were previously set to 6
1 reply 0 retweets 0 likes -
Replying to @jasonmulligan
The language version and the code completion for Node.js are different settings. We've double-checked WebStorm 2019.1.1 and the IDE sets the language level to ES6 for all new projects as it used to.
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE @jasonmulligan
Got what you mean: in WS 2018.3 the unused inspection was highlighting the second symbol even when code completion for Node.js APIs was disabled, but not in 2019.1. We will report an issue.
1 reply 0 retweets 0 likes
Here it is: https://youtrack.jetbrains.com/issue/WEB-38645
-
-
-
Replying to @jasonmulligan @WebStormIDE
the ecma version changing is unrelated as you mentioned; i brought it up to imply something under the hood changed... re-setting apps to ecma 6 is a small annoyance
1 reply 0 retweets 0 likes - 12 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.