feat: add config file validation and JSON schema #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add strict validation for ~/.mpak/config.json to catch corruption early: - Add ConfigCorruptedError for clear error reporting with config path - Validate required fields (version, lastUpdated) and types - Reject unknown fields (additionalProperties: false) - Add JSON schema at src/schemas/config.v1.schema.json - Add comprehensive test coverage for validation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
ConfigCorruptedErrorclass for clear error reporting when config is invalid~/.mpak/config.jsonthat checks required fields, types, and rejects unknown fieldssrc/schemas/config.v1.schema.jsondocumenting the config formatTest plan
npm run test:all)