✨ fix alpha order of terms, add script to detect problems and output all terms in alpha order#115
Conversation
…all terms in alpha order
| @@ -0,0 +1,213 @@ | |||
| module.exports = { | |||
There was a problem hiding this comment.
any reason to hardcode everything here, instead of basing it on a popular common shared config?
There was a problem hiding this comment.
just copying my boilerplate opinionated config. I'm fine with changing
There was a problem hiding this comment.
i'd personally prefer something minimal, and static, and largely based on something commonly used.
There was a problem hiding this comment.
Or just don't bother. There's a bunch of scripts in ecma262 and those aren't linted. Since they're almost never touched it doesn't really matter.
| ## Web compatibility/"Don't break the web" | ||
|
|
||
| ### Definition | ||
|
|
||
| A change to JavaScript is considered "**web compatible**" if it preserves the current behavior of existing websites. If it changes the behavior of existing websites, it's considered to "**break the web**". |
There was a problem hiding this comment.
a) i think this diff should be done in a separate PR, and b) i'm not sure alphabetically is the best approach
There was a problem hiding this comment.
if we're not sorting the glossary, there's no reason to merge any of this
Co-authored-by: Jordan Harband <ljharb@gmail.com> Co-authored-by: Kevin Gibbons <bakkot@gmail.com>
3 participants
next step will be incorporating the alpha verification with a new github action for status checks