You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected: no error at all
Actual Behavior: error Expected an identifier and instead saw '?'. (E030) Expected ':' and instead saw '2'. (E021) Expected an identifier and instead saw ')'. (E030) Expected an operator and instead saw '*'. (E033) Expected ')' to match '(' from line 41 and instead saw '1000'. (E020)
⬆error
The text was updated successfully, but these errors were encountered:
MaxenceDC
changed the title
double question mark marked as an error where the code can perfectly be executed (node.js)
double question mark marked as an error whereas the code can perfectly be executed (node.js)
Feb 24, 2021
Thanks for the report! The language feature you're looking for is called "nullish coalescing." Although we don't prioritize work based on the behavior of Node.js, nullish coalescing definitely satisfies our criteria for new features. Since this was previously requested in gh-3443, I'm going to close this issue to keep things tidy.
You'll be happy to hear that the feature has been implemented and will be included in the next minor release of JSHint. You can watch gh-3486 for updates on that release.
jshint version: v2.12.0
⬆code
⬆config
Expected: no error at all
Actual Behavior: error
Expected an identifier and instead saw '?'. (E030)
Expected ':' and instead saw '2'. (E021)
Expected an identifier and instead saw ')'. (E030)
Expected an operator and instead saw '*'. (E033)
Expected ')' to match '(' from line 41 and instead saw '1000'. (E020)
⬆error
The text was updated successfully, but these errors were encountered: