Predictify-org / Predictify-org/predictify-frontend
[GrantFox][Medium] Synchronize filters and pagination with URL state
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 194
- Avg merge
- 15h 38m
- Merged PRs (30d)
- 23
Description
Summary
Synchronize filters and pagination with URL state
Why this matters
Users need shareable, reload-safe market filters without invalid page combinations.
Scope
Define typed URL parameters, reset rules, validation, and stable query keys.
Acceptance criteria
- Reload restores the same filter state.
- Changing filters resets pagination.
- Invalid parameters fall back safely.
- Tests cover back/forward and shareable URLs.
Validation
Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.
Non-goals
- Typo-only, formatting-only, or documentation-only changes.
- Unrelated refactors or dependency upgrades.
- Weakening existing security, authorization, CI, or production safeguards.
Contributor application
Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.
PR requirements
Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.
Reward-readiness
This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing market filter and pagination state, their URL handling, and the relevant test entry points. Define the typed URL parameters, reset and validation behavior, then add regression coverage for reloads, back/forward navigation, shareable URLs, invalid parameters, and authorization boundaries. Done means all acceptance criteria pass and repository CI succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100