You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SearchManager has the ability to maintain multiple filter collections. For e.g. you can have separate collections for backend and frontend. But when using the search finder there's no way to tell it to which collection to use. It always uses the "default" collection.
The fix seems easy enough. Just allow passing a collection key to finder options and update the behavior to use SearchBehavior::getFilters() passing in the collection name instead of calling SearchBehavior::all() which always returns the default collection.
The text was updated successfully, but these errors were encountered:
The
SearchManager
has the ability to maintain multiple filter collections. For e.g. you can have separate collections for backend and frontend. But when using the search finder there's no way to tell it to which collection to use. It always uses the "default" collection.The fix seems easy enough. Just allow passing a
collection
key to finder options and update the behavior to useSearchBehavior::getFilters()
passing in the collection name instead of callingSearchBehavior::all()
which always returns the default collection.The text was updated successfully, but these errors were encountered: