Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rename get_next_precedence_full to get_next_precedence_default #1378

Merged
merged 1 commit into from
Aug 14, 2024

Conversation

samuelcolvin
Copy link
Contributor

@samuelcolvin samuelcolvin commented Aug 14, 2024

As discussed in #1366 (comment), follow on from #1360.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 10386985131

Details

  • 2 of 2 (100.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 89.052%

Totals Coverage Status
Change from base Build 10370172981: 0.0%
Covered Lines: 27648
Relevant Lines: 31047

💛 - Coveralls

Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

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

Thank you @samuelcolvin -- this makes sense to me

@alamb
Copy link
Contributor

alamb commented Aug 14, 2024

🚀

@alamb alamb merged commit fab834d into apache:main Aug 14, 2024
10 checks passed
@samuelcolvin samuelcolvin deleted the rename-get_next_precedence_default branch August 14, 2024 15:51
ayman-sigma pushed a commit to sigmacomputing/sqlparser-rs that referenced this pull request Nov 19, 2024
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.

3 participants