-
Notifications
You must be signed in to change notification settings - Fork 1.5k
DATAJPA-1182 - Validate method parameters on query construction. #228
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
Conversation
8bdc7b9
to
8049d03
Compare
For “In” and “NotIn” queries not providing a collection like argument results in an IllegalStateException at initialisation time. Conversely providing a collection as argument for a query other than “In” or “NotIn” also throws such an exception.
8049d03
to
69b3f25
Compare
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # Fixed URLs ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * http://maven.apache.org/xsd/maven-4.0.0.xsd with 1 occurrences migrated to: https://maven.apache.org/xsd/maven-4.0.0.xsd ([https](https://maven.apache.org/xsd/maven-4.0.0.xsd) result 200). * http://projects.spring.io/spring-data-jpa with 1 occurrences migrated to: https://projects.spring.io/spring-data-jpa ([https](https://projects.spring.io/spring-data-jpa) result 301). # Ignored These URLs were intentionally ignored. * http://maven.apache.org/POM/4.0.0 with 2 occurrences * http://www.w3.org/2001/XMLSchema-instance with 1 occurrences Original pull request: #324
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # Fixed URLs ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * [ ] http://www.apache.org/licenses/ with 1 occurrences migrated to: https://www.apache.org/licenses/ ([https](https://www.apache.org/licenses/) result 200). * [ ] http://www.apache.org/licenses/LICENSE-2.0 with 347 occurrences migrated to: https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200). Original Pull Request: #357
See Jira for review comments https://jira.spring.io/browse/DATAJPA-1182 |
For “In” and “NotIn” queries not providing a collection like argument results in an IllegalStateException at initialisation time. Conversely providing a collection as argument for a query other than “In” or “NotIn” also throws such an exception. Original pull request: #228.
Reduce loop nesting. Tweak exception message wording. Simplify tests. Original pull request: #228.
That's merged and polished now. |
For “In” and “NotIn” queries not providing a collection like argument results in an IllegalStateException at initialisation time. Conversely providing a collection as argument for a query other than “In” or “NotIn” also throws such an exception. Original pull request: spring-projects#228.
Reduce loop nesting. Tweak exception message wording. Simplify tests. Original pull request: spring-projects#228.
Hi Guys, |
@ahaczewski create an issue in Jira: https://jira.spring.io/projects/DATAJPA |
Thanks @schauder, reported as https://jira.spring.io/browse/DATAJPA-1682, hope it is enough. |
For “In” and “NotIn” queries not providing a collection like argument results in an IllegalStateException at initialization time.
Conversely providing a collection as an argument for a query other than “In” or “NotIn” also throws such an exception.