feat(compliance): list undeclared features after validation#48
Open
grdsdev wants to merge 1 commit into
Open
Conversation
When validate-compliance runs, any feature IDs absent from the sdk-compliance.yaml file are now printed to stdout so SDK owners can see at a glance what they haven't declared yet (those features default to not_implemented silently today).
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
findMissingFeatureIdstocompliance.ts— returns feature IDs in the canonical spec that are absent from an SDK's compliance file, sorted alphabetically.compliance-cli.ts(thevalidate-compliancescript) now prints these missing IDs to stdout after a successful validation, grouped under a count line.not_implemented; the exit code is unchanged — this is purely informational output.Example output
Test plan
npm testpasses (4 new tests added forfindMissingFeatureIds)