Repository navigation
Expose bounded named-export type diagnostics in preflight - #741
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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.
The value-free preflight has isolated the stop to named-export metadata. Add bounded member field-type categories and fixed boolean subchecks so the read-only path can identify the precise incompatibility without exposing export names, handler values, binding data or provider bodies.
Publisher, activation, rollback, permissions and all default paths are unchanged. Targeted safety tests cover null handler lists, invalid item types, invalid names and unknown keys; actionlint passes. This is diagnosis, not a live-fix or deployment claim.