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
LPS-129972 Simplify DSLQuery CustomSQL interactions #9917
Conversation
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:test:relevant |
ci:test:sf |
✔️ ci:test:sf - 1 out of 1 jobs passed in 4 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-129972 1 Successful Jobs:For more details click here. |
BiFunction<Expression<String>, String, Predicate> operatorBiFunction, | ||
String[] values) { | ||
|
||
if ((values != null) && (values.length == 0)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Preston-Crary do you mean if ((values == null) || (values.length == 0)) {
here? Because by the current logic, if values is null, you will get a NPE at 40e9e66#diff-39eafb03fec7101df60be56569e519a5d70deac7b42d146d6bc636ee90917554R231
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I'll fix and resend. I think I copied that over from replaceKeywords() and didn't fully update it. Thanks!
Please see #9920 |
No description provided.