fix(ci): make CI schema contracts portable and fixture expectations explicit - #8
Draft
vortsghost2025 wants to merge 6 commits into
Draft
fix(ci): make CI schema contracts portable and fixture expectations explicit#8vortsghost2025 wants to merge 6 commits into
vortsghost2025 wants to merge 6 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
- CI #251 failed on ambiguous fixture expectations - Removed unsafe filename heuristic for fixture validation - Added explicit fixtureExpectations parameter to validateCiContracts - Hosted CLI defaults to schema-contract validation (no fixtures) - Added results.ok boolean for clean pass/fail determination - 26 focused tests with temporary fixtures and real assertions - TypeScript and recovery remain visible advisories - Health and schema contracts remain required - Live runtime validation remains separate - Exactly three files changed
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
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
CI #251 exposed ambiguous fixture expectations where filename heuristics were used to classify fixtures as valid or invalid. This PR fixes that by removing the unsafe heuristic and adding explicit fixture expectations.
Changes
validateCiContracts()accepts an optionalfixtureExpectationsmap where each fixture file must have an explicit "accept" or "reject" expectation--ci-contractsmode defaults to schema-contract validation only (no fixtures), which is honest and portableschema_fail === 0andunexpected_fixture_fail === 0Test Results
CI Behavior
Files Changed
Exactly three files changed:
.github/workflows/ci.yml- TypeScript advisory, schema contracts requiredscripts/validate-schema.js- AddedfixtureExpectationsparameter,results.okscripts/test-validate-schema-ci.js- 26 genuine tests with temporary fixturesValidation
node scripts/test-validate-schema-ci.js- 26/26 passnode scripts/validate-schema.js --ci-contracts- 18/18 schemas passNotes
--no-verify