4 ms·
> Some people prefer writing JavaScript without semicolons. How do they not have bugs all over the place ? The same way that people who write with semicolons a
by WorldMaker 9y ago
> Some people prefer writing JavaScript without semicolons. How do they not have bugs all over the place ?
The same way that people who write with semicolons avoid lots of bugs: linters and transpilers and tests.
That said there is only one rule to remember when not writing semicolons, the easy to remember "winky frown" rule: all frowns must wink if they start a line/statement. ;( ;[ ;`
;(The last two are quite rare in my experience.)
It's not that tough of a rule to remember.
- gknoy 9y agoOur projects' linting rules specify no semicolons, except when necessary; this means that we will _very rarely_ write something like this when we want to iterate over a small literal array: ;['foo', 'bar'].forEach(function (f) { it(`has an ${f} field`, function () { expect(......) }) } That said, we tend to use that construct extremely rarely, such as in a few test cases where we are doing the same kinds of things on two groups of items that need different descriptions.
- WorldMaker 9y agoMost of my usages are Typescript type assertions: ;(thing as Type).methodINeed() If it weren't for these I mostly wouldn't need semicolons at all, sometimes I refactor to: const thingType = thing as Type thingType.methodINeed()