Repository navigation
Collect typing validation errors before reporting - #244
Merged
Merged
Conversation
This was referenced Nov 21, 2026
krzema12
marked this pull request as ready for review
November 21, 2026 19:00
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
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.

Refactors
validateTypings()so action-level validation problems (lowercase names, schema issues, missing manifests, input/output mismatches) are collected into a list instead of being printed and failed on immediately. At the end of the run all issues are printed together, sorted, with the affected action included in each message.No behavior change: the same conditions still fail validation. Split out of #239 to keep the baseline change focused.