-
Notifications
You must be signed in to change notification settings - Fork 29
Avoid duplicate column suggestions in search bar #556
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
81f069d
to
168bcc8
Compare
168bcc8
to
e38a591
Compare
110f51e
to
d24ce21
Compare
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.
A key feature of this procedure is to only produce as much results as necessary. This change produces all columns of all relations at once, making it more inefficient.
Please think of a different solution, maybe along the lines of filtering out duplicate relation targets in the sub-procedures.
`ObjectSuggestions::collectFilterColumns()` returns duplicate column names due to the sub-relations of the joined models. Hence, `ObjectSuggestions::fetchColumnSuggestions()` returns duplicate suggestions for column names for the search bar. This fix solves this issue by resolving the redefinition of the method parameter `$model` in `ObjectSuggestions::collectFilterColumns()` and not registering the duplicate models in `ObjectSuggestions::collectRelations()`.
d24ce21
to
335c08d
Compare
ObjectSuggestions::collectFilterColumns()
returns duplicate column names due to the sub-relations of the joined models. Hence,ObjectSuggestions::fetchColumnSuggestions()
returns duplicate suggestions for column names for the search bar. This fix solves this issue by resolving the redefinition of the method parameter$model
inObjectSuggestions::collectFilterColumns()
and not registering the duplicate models inObjectSuggestions::collectRelations()
.fix #534