1. Feature Overview
Let a logged-in user view their saved filter combinations (most recent first, up to 10) as cards showing the applied criteria, with the server always returning a valid, cleanly re-serialized filter object.
2. User Stories
- As a user,
- I want to see my recent filter combinations as cards,
- So that I can re-run a specific filtered search with one click.
3. Acceptance Criteria
Scenario 1: List My Filter Cards
- Given I am logged in and have saved combinations
- When I open the recent filters section
- Then I see up to 10 cards, most recent first, each showing a valid filter object.
Scenario 2: Server Re-Serializes the Payload
- Given a saved combination exists
- When the list loads
- Then I always receive a clean, valid filter object — never raw or partial JSON.
Scenario 3: Corrupt Legacy Record Does Not Crash
- Given a stored record contains corrupted or out-of-schema data
- When the list loads
- Then the record is skipped (or shown sanitized) and the page still works.
Scenario 4: Empty History
- Given I have never saved a combination
- When I open the section
- Then I get an empty list with a 200 response, not an error.
Scenario 5: Re-Run With No Current Matches
- Given a saved filter no longer matches any property
- When I re-run it
- Then I get an empty result list while the filter card stays intact.
Scenario 6: Unauthenticated
- Given I have no valid session
- When I request the list
- Then access is denied.
4. Resources & References
1. Feature Overview
Let a logged-in user view their saved filter combinations (most recent first, up to 10) as cards showing the applied criteria, with the server always returning a valid, cleanly re-serialized filter object.
2. User Stories
3. Acceptance Criteria
Scenario 1: List My Filter Cards
Scenario 2: Server Re-Serializes the Payload
Scenario 3: Corrupt Legacy Record Does Not Crash
Scenario 4: Empty History
Scenario 5: Re-Run With No Current Matches
Scenario 6: Unauthenticated
4. Resources & References