Repository navigation
Add versioned CTRF schema validation - #86
Merged
Merged
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
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.
Updates ctrf-js to support validation against every published CTRF specification version:
0.0.10.0.20.0.30.0.40.1.0latest, which resolves to0.1.0Each schema is copied exactly from its corresponding CTRF release. Schema loading now uses the complete semantic version so patch releases can have distinct validation behaviour.
Retry-history validation is version-aware: the stricter rules apply to
0.0.4and0.1.0, while earlier versions retain their historical behaviour.This change also:
0.1.0as the current and default specification version.validate(),isValid(), andvalidateStrict().SchemaSelectorandSupportedSpecVersion.0.4.0.Verification