| 12:50 | <eemeli> | I'm starting to draft spec text for the Intl.MessageFormat proposal, and thought I'd check: Is there anything like a style guide available for ECMA-262/ECMA-402, or is that "just" implicit from what the specs currently look like? I recall some vague conversations about such a thing, but now I can't be sure if those were of a thing that actually exists already. |
| 15:55 | <ptomato> | it doesn't exist, but it's something I'd like to work on. there is a PR with the very beginning of one, but it's stalled: https://github.com/tc39/how-we-work/pull/119 |
| 16:00 | <eemeli> | Thank you, that's exactly what I recall having come across earlier. Having that guidance be more discoverable would be great. |
| 16:20 | <bakkot> | eemeli: using --lint-spec when building with ecmarkup will also check some conventions, and running npx emu-format spec.html will run a formatter which will enforce some more |
| 17:57 | <Michael Ficarra> | eemeli: A lot of our conventions are also informally listed here: https://github.com/tc39/ecmarkup/issues/173 |
| 17:57 | <Michael Ficarra> | the 262 editors would like to eventually document our editorial conventions more formally on the 262 wiki |
| 17:58 | <Michael Ficarra> | it's just been hard to find time to work on that |
| 18:04 | <eemeli> | Michael Ficarra: That's an excellent resource, thank you! |