18:24
<shu>
i guess this is the first time i've done modern JS development, for ecmarkup
18:24
<shu>
i am not a fan of these eslint rules
18:30
<shu>
bakkot Michael Ficarra https://github.com/tc39/ecmarkup/pull/362 should have all the fixes and changes we discussed on the call, minus docs
18:30
<shu>
i didn't see a structured header doc section in the existing docs, and i didn't feel like writing one :P
18:35
<shu>
also the <emu-meta> tag now does go over the entire invocation
18:36
<shu>
e.g. <emu-meta suppress-effects="user-code">AO()</emu-meta>
18:36
<shu>
the xref is just checking for parentElement. additionally, putting it around just the AO name actually doesn't work correctly, because then the autolinker can't tell it's an invocation
18:37
<shu>
since the check for that is just the real naive "is the next character a '('"
19:11
<bakkot>
npm run lint -- --fix will fix a majority of the things the linter complains about
19:11
<bakkot>
which is a lot less painful than fixing them yourself
19:12
<bakkot>
re: docs, that's fine, I'll add docs for structure headers and effects at some point
20:02
<shu>
ah, good tip, didn't know about --fix
22:21
<ljharb>
you can also configure your editor to automatically run eslint autofix on save
22:22
<shu>
my .emacs is an ossified relic
22:22
<shu>
if i ever have to be productive in a language other than C++ i am screwed
22:23
<ljharb>
i'm sure you can configure your operating system to do it too :-p
22:29
<bakkot>
you can also configure your editor to automatically run eslint autofix on save
I've never understood how anyone can stand this - saving shouldn't change the file; I'm saving precisely because I am at a point where I do not want it to change!
22:29
<ljharb>
¯\_(ツ)_/¯ for me it's that that's the point where i don't want the semantics to change, autofixes don't change the semantics
22:30
<ljharb>
but you could ofc run it on the command line manually if you want, nbd