Skip to content

Conversation

@DecimalTurn
Copy link
Member

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.

@github-actions
Copy link

github-actions bot commented Aug 17, 2025

PR Preview Action v1.6.2
Preview removed because the pull request was closed.
2025-09-03 16:27 UTC

@ell1e
Copy link

ell1e commented Aug 17, 2025

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.

Copy link
Contributor

@Alhadis Alhadis left a 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.

@DecimalTurn
Copy link
Member Author

DecimalTurn commented Aug 31, 2025

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.

@DecimalTurn
Copy link
Member Author

I think somehow accepting changes via the GitHub interface (2615c83) is causing the pr-preview to fail 😔, but I'm not too worried...

@DecimalTurn DecimalTurn merged commit 4a80657 into main Sep 3, 2025
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants