Repository navigation
refactor(nodes): reuse MapPayloads in common nodes - #214
Merged
Merged
Conversation
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.
OCR, JSON parsing and rule matching repeated batch traversal and request provenance handling. Reuse the existing
MapPayloadshelper in these three production implementations while preserving their model calls, error policies and output behavior.Extend regression coverage for JSON parse diagnostics and regex execution failures, including provenance and absence of partial output.
Validation: the canonical local gate passed with 456 tests passed and 5 asset-dependent tests skipped (461 total).