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

fix: check that contextValue starts with #240

Conversation

chriswk
Copy link
Member

@chriswk chriswk commented May 6, 2024

There had been an inversion of variable usage for one of our cases in the matcher. This PR makes sure to compare contextValue to see if it starts with the requested value in the constraint, instead of the other way around.

fixes #238

There had been an inversion of variable usage for one of our cases in
the matcher. This PR makes sure to compare contextValue to see if it
starts with the requested value in the constraint, instead of the other
way around.

fixes #238
Copy link
Member

@sighphyre sighphyre left a comment

Choose a reason for hiding this comment

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

Nice fix, silly bug

@chriswk chriswk merged commit 0e23677 into main May 6, 2024
4 checks passed
@chriswk chriswk deleted the 238-string-operator-str_starts_with-is-not-evaluated-correctly-when-case-sensative-is-disabled branch May 6, 2024 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

String operator STR_STARTS_WITH is not evaluated correctly when case-sensative is disabled
2 participants