Improve transformation error reporting and node validation #78
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
- Introduce `Core.Result` type for collecting both valid and invalid nodes - Update transformation pipeline to return invalid vertex and beam nodes - Add `putErrorLine` and `reportInvalidNodes` in IOUtils for stderr reporting - Propagate bad node tracking through VertexExtraction and SupportVertex modules - Update Transformation logic to handle (badVertexNodes, badBeamNodes, Node) - Add Core.Result to Cabal file for build inclusion
webdevred
force-pushed
the
better-transformation-error-messages
branch
from
a418d9b to
6b3ad6e
Compare
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.
Core.Resulttype for collecting both valid and invalid nodesputErrorLineandreportInvalidNodesin IOUtils for stderr reporting