Add links to ECMA-262 entities #112
Comments
|
Just submitted a pull request that happens to also address this: #132 |
Huxpro
added a commit
to Huxpro/jsx
that referenced
this issue
Feb 23, 2022
This is the first step to revamp this repo: [ecmarkup](https://github.com/tc39/ecmarkup) is TC39's official tool for specifying syntax and semantics for ECMAScript. I proposed that we should adopt it because it has several favorabilities than the current approach (`README.md` + a `gh-pages` website living in the `websitescript` branch): 1. The resultant `index.html` has a similar looks and feels with the official ECMA-262 spec. 2. It uses [Grammarkdown](https://github.com/rbuckton/grammarkdown) which is not only convenient to write but more importantly, can enforce the grammar to be more formal. 3. It provides links to ECMA-262 out of the box (closed facebook#112). Furthurmore, I can use `<ins>` to make "extension" points explicit. One possible concern it that it'll make this too like a ECMAScript proposal, but I think we mediated by opting-out from the "stage-N proposal" heading, and by explicitly calling out our intention in the "Introduction" section. In addition, - Link to JXON is updated since the original link no more existed. - Parser and Transpiler section is dropped from the "spec" website. - Facebook, Inc. is updated to Meta Platform, Inc everywhere. Once this is merged, we can switch to `main` to host Github Pages.
Merged
Huxpro
added a commit
that referenced
this issue
Feb 24, 2022
* Migrate to ecmarkup This is the first step to revamp this repo: [ecmarkup](https://github.com/tc39/ecmarkup) is TC39's official tool for specifying syntax and semantics for ECMAScript. I proposed that we should adopt it because it has several favorabilities than the current approach (`README.md` + a `gh-pages` website living in the `websitescript` branch): 1. The resultant `index.html` has a similar looks and feels with the official ECMA-262 spec. 2. It uses [Grammarkdown](https://github.com/rbuckton/grammarkdown) which is not only convenient to write but more importantly, can enforce the grammar to be more formal. 3. It provides links to ECMA-262 out of the box (closed #112). Furthurmore, I can use `<ins>` to make "extension" points explicit. 4. It has single source of truth and prevent from syncing issue between the README and website (close The syntax in website is missing JSXFragment as JSXChild #128) One possible concern it that it'll make this too like a ECMAScript proposal, but I think we mediated by opting-out from the "stage-N proposal" heading, and by explicitly calling out our intention in the "Introduction" section. In addition, - Link to JXON is updated since the original link no more existed. - Parser and Transpiler section is dropped from the "spec" website. - Facebook, Inc. is updated to Meta Platform, Inc everywhere. Once this is merged, we can switch to `main` to host Github Pages.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys,
I was reading the spec of JSX and noticed that there were some entities from ECMA-262 such as
IdentifierStart, etc. Do you mind if I add links from them to ECMA-262? It will make the spec a bit more handy.The text was updated successfully, but these errors were encountered: