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
Describe the bug
In the new WIP CatalogSearchView, the pager and page part of the URL does not reset when a search term is added to the query. So if an initial query has n pages of results, and you navigate to the last page, then you add a search term that results in < n pages, then the CatalogSearchView stays on page n but that page is empty.
To Reproduce
Steps to reproduce the behavior:
The new Catalog Search is not available on any production repos at the time of writing, so run MetacatUI locally and set the useDeprecatedDataCatalogView config option to false.
In the catalog, search for any term that gives a result with at least a few pages.
Switch to the last page.
Add another search term that gives results, but fewer pages than previously.
See that the list is now empty, and the page hasn't reset to page 1.
Expected behavior
I think the expected behaviour would be for the catalog to switch back to the first page when a new filter/term is added to the search. This should be reflected in the URL as well.
Screenshots
Additional context
I think this should be resolved before we release the new CatalogSearchView, so this issue blocks #1520 and #1720
The text was updated successfully, but these errors were encountered:
Describe the bug
In the new WIP CatalogSearchView, the pager and page part of the URL does not reset when a search term is added to the query. So if an initial query has
n
pages of results, and you navigate to the last page, then you add a search term that results in< n
pages, then the CatalogSearchView stays on pagen
but that page is empty.To Reproduce
Steps to reproduce the behavior:
useDeprecatedDataCatalogView
config option to false.Expected behavior
I think the expected behaviour would be for the catalog to switch back to the first page when a new filter/term is added to the search. This should be reflected in the URL as well.
Screenshots
Additional context
I think this should be resolved before we release the new CatalogSearchView, so this issue blocks #1520 and #1720
The text was updated successfully, but these errors were encountered: