-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Definition for frontmatter id tags #477
Comments
I think it should just be "id" |
Yes, it makes sense. I'll update the title and example. |
I think this is a good idea. The test harness doesn't use the current I also agree with @littledan that this way we wouldn't have to keep up with changes in section numbers. |
+1 |
I'm a little late to the party, but I'd like to know more about the decision to use the name There wasn't any discussion about why the change was made, so I thought I'd ask here. |
Any of those names sounds good to me. |
I would like to reopen this issue. After an internal - and informal - conversation with @jugglinmike and @rwaldron, It's been clear how It's still early to fix this up. |
@leobalter I'm OK with |
As mentioned at #472 (comment):
Based on this, and as it's easy to locate the section ids on tc39/ecma262 on each of the
emu-clause
tags, which are expected to be unique, I believe we can use the respective hash id for the Frontmatter'sid
and further versions:this value can be converted to links that could be found anywhere:
This reference works good and it's still compatible with the previous formats, as won't conflict with the recently adopted
es7id: pending
value, which can be easily replaced byid: pending
and it's still useful for anything on Stage 3 and it's not on the draft yet.@goyakin, do you like this idea?
The text was updated successfully, but these errors were encountered: