-
Notifications
You must be signed in to change notification settings - Fork 3
Clarify goal of the spec + trailing commas seperate page #7
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
Conversation
|
|
Thank you, I think this is a useful clarification. I personally won't adhere to this specification then since I don't consider it useful for my requirements, but I'm glad there seems to be no room for confusion anymore. |
Alhadis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Editorial nits, some of them less important than others.
Co-authored-by: John Gardner <gardnerjohng@gmail.com>
|
Thanks @Alhadis for taking the time to make a review. I hope I've addressed your comments and suggestions in a satisfactionary manner. I'll probably merge this soon, but feel free to reply to my comments. Furthermore, there's also the option to discuss and make edits in another PR if pertinent. |
|
I think somehow accepting changes via the GitHub interface (2615c83) is causing the pr-preview to fail 😔, but I'm not too worried... |
The additions here aim to clarify the goal of the spec:
Provide a definition in accordance with jsonc-parser.
To avoid any ambiguity regarding whether or not a parser needs to implement trailing commas, a separate page is introduced to add more details about them, while keeping the spec short and clear. This should address #5.