Issue #2176 - Skip to lookup unwanted Querydsl properties#3471
Closed
kamilkrzywanski wants to merge 1 commit intospring-projects:mainfrom
Closed
Issue #2176 - Skip to lookup unwanted Querydsl properties#3471kamilkrzywanski wants to merge 1 commit intospring-projects:mainfrom
kamilkrzywanski wants to merge 1 commit intospring-projects:mainfrom
Conversation
Signed-off-by: Kamil Krzywański <kamilkrzywanski01@gmail.com>
spring-projects-issues
added
the
status: waiting-for-triage
mp911de
added
status: declined
Member
|
The problem isn't |
Contributor
Author
|
@mp911de Thanks for the suggestion — that was actually my first idea as well. However, in practice it would require additional reflection for every single field/property, which adds overhead and complexity. That’s why I went with an approach that avoids extra per-field reflection. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix for #2176