People who maintain such a linting tool can feel free to recommend a style that works well with the tool, as long as they advocate that the style is only used with a linter that mitigates the hazards.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
“But standardjs doesn’t do it this way” was an *incredibly* strange argument to see in the context of discussing the actual language spec.
-
Good reason to not call it "standardjs"
-
directly from my good old open letter post
... how I've always seen that project's name
https://hackernoon.com/an-open-letter-to-javascript-leaders-regarding-no-semicolons-82cec422d67d …pic.twitter.com/3re8jWuRe0
End of conversation
New conversation -
-
-
As someone who is both A) a representative on TC39, and B) a maintainer of a linting tool: I agree with both of your tweets, with no exceptions
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I just had Edge refuse to render my whole site potentially over a trailing comma
#SCRIPT1028 -
Was it in function arguments? If so keep in kind those haven’t always been a feature and it’s possible it hasn’t been implemented in edge yet
-
Looks like there's an open issue for what I am experiencing:https://github.com/glimmerjs/glimmer.js/issues/8 …
End of conversation
New conversation -
-
-
I disagree with the assertion that either semicolons or semicolonless _require_ a linter
-
semicolon style _requires_ a linting tool in the same way that standardjs style requires one: when a semicolon was omitted but necessary
-
Example: return myVal; Will be: return; // ASI myVal; The problem I have with ASI is that I need to know how it works, no matter what style I use, or I can get bugs. Same thing with var/let/const and lambda bodies/expressions. The last one is my most common day-to-day bug.
-
I disagree, the ASI is simply a syntax correcting mechanism. The return statement does not allow a line terminator: https://www.ecma-international.org/ecma-262/5.1/#sec-12.9 …
-
Are you disagreeing with the need to know how ASI works? And as evidence you link to how it works..? Sorry, I'm a bit sick today, so maybe I'm misunderstanding.
-
I am linking towards the syntax of the return statement. The rules of the ASI are that it kicks in whenever there's an "offending token". IMHO, you don't really need to know how the ASI works, just know the syntax. That might be cherry picking sorry if so
-
since omitting ; doesn’t generate a runtime err, i proffer that you *do indeed* need to know about/how ASI works. regardless of style choice
-
as longs as ASI exists, using or not using semicolons doesn’t change your safety either style you choose, you need a linter: either a no-semi linter to warn when you missed one that _matters_ or a semi-linter that warns when you miss one _anywhere_
- 1 more reply
New conversation -
-
-
Do you have an example? I’m having trouble understanding how any JS style would *require* a linter.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
No JS style literally requires using a linting tool, but regardless of style, a linting tool is a "must have" for JS - they can catch a bunch of problems that are hard to spot in any style.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.