Skip to content

fix: explain malformed blueprint JSON errors - #32

Merged
devi5040 merged 1 commit into
devi5040:masterfrom
11suixing11:fix/malformed-blueprint-errors
Jul 27, 2026
Merged

fix: explain malformed blueprint JSON errors#32
devi5040 merged 1 commit into
devi5040:masterfrom
11suixing11:fix/malformed-blueprint-errors

Conversation

@11suixing11

Copy link
Copy Markdown
Contributor

Summary

  • report malformed blueprint JSON with the blueprint path, line/column when available, and the original parser error
  • add a short validation hint instead of only printing Invalid Json in blueprint file
  • add a npm test script with a node:test regression for the formatter

Fixes #30

Verification

  • npm test
  • npm run build
  • npm run lint
  • CLI smoke test with malformed JSON exits 1 and prints the path, line/column, parser error, and validation hint
  • git diff --check

Note: npm ci reports 2 existing audit findings (1 low, 1 high); I did not change dependencies in this focused fix.

@devi5040
devi5040 self-requested a review July 27, 2026 07:53

@devi5040 devi5040 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved the PR.

@devi5040
devi5040 merged commit 3149ea9 into devi5040:master Jul 27, 2026
4 checks passed
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.

[Bug]: Improve error message for malformed blueprint JSON

2 participants