CoderMuffin
CoderMuffin
@strager @vegerot maybe it should be a warning unless it is immediately compared to "undefined"? maybe a config setting could be added to disable it if it is too aggressive
Hi @strager, I would be interested in tackling this issue :) Are strings within the parser encoded in any specific format (UTF-8, UTF-16\*\*) or does it need to be able...
Hi @strager, Sorry for the ping, just wondering if there was any update on this? Thanks :)
Hi @strager, I would love to tackle this issue if that's ok :)
@NabiKAZ This can also be resolved by removing the `default`: ```js const JSEncrypt = require("jsencrypt"); //note the missing ".default" let crypt = new JSEncrypt(); // etc. ```
@singalhimanshu yes, you can compare the Expression::Literal->span()->string_view() to each element of the array. The detection code for a similar diagnostic which might help can be seen here: [src/quick-lint-js/fe/parse.cpp:524](https://github.com/quick-lint/quick-lint-js/blob/d09a1a72675fd1673dac5793b099c6169698829d/src/quick-lint-js/fe/parse.cpp#L524)
Not sure what to do regarding the failing docs check on E0343 and E0342, is there any way to declare that the new E0459 should also be triggered here?
@laveenaBachani Maybe try reverting the version string? (i.e. `"Visual Studio 16 2019"` instead of `"Visual Studio 17 2022"`) If that doesn't work, could you maybe install VS2019?
@JalonSolov Should be working here https://play.vlang.io/p/8170c26143