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 start parameter in the graphql query of our search client's search method, had until now assumed to be start page and passing a page number would return the results of size count from that page.
start actually refers to the index of individial serach results so to get page would be
"start": count * page,
need to implement the fix in the catalogue package.
This bug is presenting itself in the paginated results of find-moj-data
To Reproduce
make a search with more than 20 results
got to page 2
see top result is 2nd from top result from previous page
Expected Behaviour
subsequent pages of search results display unique results. Should match the page results as seen in datahub UI
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug.
The start parameter in the graphql query of our search client's search method, had until now assumed to be start page and passing a page number would return the results of size
count
from that page.start actually refers to the index of individial serach results so to get page would be
need to implement the fix in the catalogue package.
This bug is presenting itself in the paginated results of
find-moj-data
To Reproduce
Expected Behaviour
subsequent pages of search results display unique results. Should match the page results as seen in datahub UI
Additional context
No response
The text was updated successfully, but these errors were encountered: