Pagination does not respect filters

Open
#260 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Reproduce the issue by applying the search and write-mode filters, then using the “next page” button. Trace how the active filters are carried into pagination and verify that the second page still shows only matching content; done means pagination preserves every active filter.

Written by the indexing model from the issue text.

Description

bug

The "next page" button works as if there is no active filter in the view - it shows the results with no currently active filters applied.

image

That is the 2nd page. Notice the "search" field and the "write mode" filter. None is respected for the content being displayed.

Dominant language
TypeScript
Stars
12
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AbsaOSS/spline-ui

All issues in AbsaOSS/spline-ui

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.