hackforla / hackforla/tdm-calculator
Dev: Filters should be maintained independently per tab (TDM Plans vs Deleted TDM Plans)
- Dominant language
- JavaScript
- Stars
- 68
- Forks
- 47
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 25
Description
### Overview
We need to implement independent filters for the TDM Plans and Deleted TDM Plans tabs on the My TDM Plans page so that users can manage the results independently.
### Details
When a user applies filters in one tab (e.g., TDM Plans), those filters should not affect another tab (e.g., Deleted TDM Plans).
Each tab should maintain its own independent filter state.
Expected behavior:
- Filters applied in the TDM Plans tab remain only in that tab
- Filters applied in the Deleted TDM Plans tab remain only in that tab
- Switching between tabs does not carry over filters
- Each tab “remembers” its own last-used filter state
### Action Items
- [ ] Assign yourself to the development issue.
- [ ] Move the development issue from the Prioritized Backlog to In Progress.
- [ ] Developer Action: Implement the change.
- [ ] Create a PR, if applicable.
- [ ] add the before and after images to the slide in staging
- [ ] Once the PR has been approved, use it to close this issue. If there is no PR is associated with this issue, close this issue after lead signoff.
### Resources/Instructions
- Related issue: #3126
#### Staging and Release decks
- [Staging Deck](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/)
- [Staging slide, 3158](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/edit?slide=id.g3defaf3d508_51_14#slide=id.g3defaf3d508_51_14)
- Release Deck
- [2025-MM-DD Release deck, slide ISSUE NUMBER]
Contributor guide
Research direction
Start on the My TDM Plans page by tracing how filter state is stored and applied for the TDM Plans and Deleted TDM Plans tabs. Review related issue #3126 for context. Done means each tab preserves its own last-used filters, switching tabs does not carry filters across, and the behavior is verified in staging with before-and-after images added to the staging slide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100