Repository navigation
fix: support shared compatibility keys - #17
Merged
Merged
Conversation
3ru
force-pushed
the
fix/compat-key-overlap
branch
from
October 4, 2026 08:29
a69b1f6 to
52b2cb7
Compare
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
1 participant
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.
Retain every feature membership for shared compatibility keys. Decode dataset inputs, reject conflicting or malformed rows, and verify the raw dataset against the pinned package.
Depends on #16. Validation: npm run validate; TypeScript integration gate; package dry run.