Repository navigation
fix: keep empty-fixture lint exemption after non-ASCII text - #829
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.
Why
In 0.119.0, SQL tests whose empty-fixture CTEs (
SELECT * FROM __EMPTY_FIXTURE()) follow non-ASCII text were reported by SQBRSQL021. Non-ASCII SQL takes the Python lint preparation path, where the formatter's new spelling protection replaced the intrinsic call with a placeholder, so the empty-fixture exemption no longer matched.Changes
__empty_fixture,__cursor_startand__cursor_end, matching the native path's case and spacing policy.Verification
make test(7,752 passed) andmake check-ci.format --checkresults are identical to the verified 0.119.0 run.