Fix issue with collection attributes not being recognized #221
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jzrilic
reviewed
Sep 20, 2024
nrich-search/src/test/java/net/croz/nrich/search/repository/support/JpaQueryBuilderTest.java
Outdated
Show resolved
Hide resolved
… join instead of exsits query by default
agrancaric
force-pushed
the
bugfix_fixPluralAttributeRestriction
branch
from
9291b09 to
588bc34
Compare
jzrilic
approved these changes
Sep 20, 2024
jzrilic
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basic information
2.6.0
nrich-search
Additional information
Description
Summary
Fix issue with collection attributes not being recognized and using a join instead of exist query by default
Details
Fix issue with collection attributes not being recognized and using a join instead of exist query by default
Related issue
Types of changes
Checklist
My change requires a change to the documentationI have updated the documentation accordingly