Skip to content

docs(check-skill-examples): drop the stale zero-jsonc-fences claim #7631

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.

Sign up for GitHub

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

Merged
os-steve merged 1 commit into from
Sep 4, 2026
+3 −2
Merged

docs(check-skill-examples): drop the stale zero-jsonc-fences claim #7631

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions scripts/check-skill-examples.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -919,8 +919,9 @@ function stripTrailingCommas(source) {
* tolerant parser here would bless a file no `JSON.parse` in the product would
* accept. `jsonc` gets comments and trailing commas removed first, and nothing
* else: that is the whole of what the `jsonc` dialect adds over `json` for the
* shapes a guide writes. There are zero `jsonc` fences in the corpus today; the
* language is recognised so that adding one is not a silent no-op.
* shapes a guide writes. The `jsonc` branch is exercised by fences already in
* the corpus, not merely reserved for a hypothetical one; re-derive the
* population with `--measure`.
*/
export function parseJsonFence(body, language) {
const text = language === 'jsonc' ? stripTrailingCommas(stripJsonComments(body)) : body;
Expand Down
Loading