Fix formatter test setup and ignore condition #132
Merged
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.
While extending the parser functionality, I encountered some issues with the existing formatter test suite:
The
formatter_test.go
was sharing aformatEnvironment
across test cases. This led to state-related bugs due to shared state between tests. Now, a newformatEnvironment
is created for each test to ensure independence and prevent errors that could arise from shared state.There was a typo in the
.ignore
file naming (003.ignroe
), and the ignore condition logic was incorrect. The tests incorrectly reported failures when an.ignore
file was present and an output mismatch occurred. This has been remedied so that now, presence of an.ignore
file will result in the output being logged instead of causing a failing test.