Report template processing errors#110
Merged
glopesdev merged 4 commits intoharp-tech:mainfrom Mar 13, 2026
Merged
Conversation
Any errors raised during the code generation process are surfaced through a single collection. Each code generation target is marked with its default target file name.
In case the error collection is not empty, an assertion error is raised concatenating all reported errors.
Added infrastructure for matching expected error messages against template processing errors. Added tests for invalid IO pin configuration.
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.
Surface any errors raised during the code generation process through a single
Errorsproperty in each generator API, and include the target file name of the template raising the code generation error for improved debugging experience.Added assertions to ensure no errors are raised during code generation tests. In case the error collection is not empty, an exception is thrown concatenating all reported errors.
Finally, regression tests were added for expected generator errors. Infrastructure is provided for matching expected error messages against template processing errors and added tests for invalid IO pin configuration.