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
It looks like this was implemented sometime: there is currently code to filter out non-selectable items.
However, it has a bug. When browsing rather than searching, the pattern asks the server for all types, and then filters them on the client side. This is so that it can include folderish types in the results. But, if there are multiple pages of results and all of the results in the first page are not selectable, then the pattern shows a "no results" message even if there are valid results on later pages.
I suspect that the right solution is to configure the pattern with a list of folderish types, and make it ask the server for the union of folderish and selectable types when browsing, so that this filtering happens on the server side rather than the client side.
The reasoning was for the behavior was as @davisagli described. I wasn't aware of the bug.
Doing the filtering server side (using the is_folderish index) sounds good.
If one passes the RelatedItems pattern a list of 'selectableTypes', it does not make sense to show non-folderish types not in this list.
The text was updated successfully, but these errors were encountered: