We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
boolean nativeQuery
checkHasNamedParameter
StringQueryUnitTests
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
private void checkHasNamedParameter(String query, boolean expected, String label, boolean nativeQuery) { List<ParameterBinding> bindings = new ArrayList<>(); StringQuery.ParameterBindingParser.INSTANCE.parseParameterBindingsOfQueryIntoBindingsAndReturnCleanedQuery(query, bindings, new StringQuery.Metadata()); assertThat(bindings.stream().anyMatch(it -> it.getIdentifier().hasName())) // .describedAs(String.format("<%s> (%s)", query, label)) // .isEqualTo(expected); }
I noticed while reading the test code that the boolean nativeQuery parameter in the checkHasNamedParameter is not being used.
It seems unnecessary in this method. Would it be okay to remove this parameter and update the methods that use it accordingly?
The text was updated successfully, but these errors were encountered:
Remove unnecessary parameter.
8d7c0c0
Remove unnecessary boolean nativeQuery from checkHasNamedParameter of StringQueryUnitTests class. Signed-off-by: hgh1472 <hgh1472@naver.com> Closes #3827 Original pull request: #3828
4b34ac0
329c5f9
mp911de
Successfully merging a pull request may close this issue.
StringQueryUnitTests.java
I noticed while reading the test code that the
boolean nativeQuery
parameter in thecheckHasNamedParameter
is not being used.It seems unnecessary in this method. Would it be okay to remove this parameter and update the methods that use it accordingly?
The text was updated successfully, but these errors were encountered: