Switch from tab to 4 spaces in baseline #152
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
|
@jsh9 Any hints here? I don't have easy access to a windows box to sort the path issue. Any guidence appreciated. - brad |
jsh9
reviewed
Jul 18, 2024
|
Thank you so much for making this change! Sorry it took me a while to finally get to it. I'll publish it in a new version in the next 1-2 days. |
|
Thanks for the cleanup and style fixes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Switch from a tab to 4 spaces in the baseline file for each violation.
Given the
strip()in theparseBaselinefunction, there should be no issue with backward compatiblity.This is confirmed with an additional test added.
Closes #143