feat: add flag schema inspection#65
Draft
privatenumber wants to merge 1 commit into
Draft
Conversation
📊 Package size report 9%↑
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
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.
Context
Cleye needs to reason about the same flag recognition surface that type-flag uses internally for conflict checks, strict-mode suggestions, and help metadata. Today that requires Cleye to reconstruct parser rules for camel/kebab names, aliases, single-character flags, and boolean negation.
This PR proposes the smallest type-flag-side inspection surface for that integration work.
Changes
inspectFlags(schema, options?)InspectFlagsOptionsandInspectedFlagno*flag precedence over negationtypeFlag()API Sketch
typeFlag()does not allocate this metadata during normal parsing. Inspection is opt-in and should remain tree-shakable for consumers that do not import it.Follow-Up
If this API shape looks reasonable, the next step is to prototype Cleye against it and measure whether it removes local recognition duplication without growing the emitted bundle.