Add "whereNotIn" native support to Meilisearch, Database and Collection engines #760
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.
I have introduced the "whereNotIn" support to the Scout query builder to be used with Meilisearch, to continue with elegant and readable code following Laravel's coding standards:
Eliminates the need for previous hackish workarounds, example:
Transformed into:
I apologize for not including Algolia support, since its paid service and I don't have an active account with them to write and run all tests.
Best
Edgar Pimienta