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
To make the new CatalogSearchView behaviour consistent with the old DataCatalogView, it needs to do the following:
In the following case, the CatalogSearchView should automatically switch back to the last viewed page of the search results: A user performs a search, switches to page n of the results, then clicks to navigate somewhere else in the app (e.g. clicks on a dataset), then clicks the back button. The url will be formatted as {REPO-URL}/data/page/{n}, and thus the search results should return to page n
When a user is on page n of search results and refreshes the page, the CatalogSearchView should remove the page/{n} part of the URL and return to the first page of the results. This is the current behaviour of the DataCatalogView. Alternatively, we could navigate to page n in that case.
When a query is appended to the end of the URL (e.g. {REPO-URL}/data/query=test), the catalog should automatically trigger a search for that query.
When fixing this issue, we should ensure that we don't re-introduce the bugs described in #971 and #723.
(Ideally the query would also be added to the URL so that a user could navigate back to the same search results, but this is an enhancement for another issue)
The text was updated successfully, but these errors were encountered:
To make the new CatalogSearchView behaviour consistent with the old DataCatalogView, it needs to do the following:
n
of the results, then clicks to navigate somewhere else in the app (e.g. clicks on a dataset), then clicks the back button. The url will be formatted as{REPO-URL}/data/page/{n}
, and thus the search results should return to pagen
n
of search results and refreshes the page, the CatalogSearchView should remove thepage/{n}
part of the URL and return to the first page of the results. This is the current behaviour of the DataCatalogView. Alternatively, we could navigate to pagen
in that case.{REPO-URL}/data/query=test
), the catalog should automatically trigger a search for that query.When fixing this issue, we should ensure that we don't re-introduce the bugs described in #971 and #723.
(Ideally the query would also be added to the URL so that a user could navigate back to the same search results, but this is an enhancement for another issue)
The text was updated successfully, but these errors were encountered: