Skip to content

Conversation

keraion
Copy link
Contributor

@keraion keraion commented Oct 9, 2024

Brief summary of the change made

This fixes the ordering of lexing some of the JSON operators in the postgres dialect. This was preventing some operators from being lexed properly.

Are there any other side effects of this change that we should be aware of?

None

Pull Request checklist

  • Please confirm you have completed any of the necessary steps below.

  • Included test cases to demonstrate any code changes, which may be one or more of the following:

    • .yml rule test cases in test/fixtures/rules/std_rule_cases.
    • .sql/.yml parser test cases in test/fixtures/dialects (note YML files can be auto generated with tox -e generate-fixture-yml).
    • Full autofix test cases in test/fixtures/linter/autofix.
    • Other.
  • Added appropriate documentation for the change.

  • Created GitHub issues for any relevant followup/future enhancements if appropriate.

Copy link
Contributor

github-actions bot commented Oct 9, 2024

Coverage Results ✅

Name    Stmts   Miss  Cover   Missing
-------------------------------------
TOTAL   18515      0   100%

236 files skipped due to complete coverage.

Copy link
Member

@alanmcruickshank alanmcruickshank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 🚀

@alanmcruickshank alanmcruickshank added this pull request to the merge queue Oct 9, 2024
Merged via the queue into main with commit 0a32baa Oct 9, 2024
29 checks passed
@alanmcruickshank alanmcruickshank deleted the postgres_json_operator_ordering branch October 9, 2024 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fails to parse ?& array['foo']
2 participants