psa-systems/mokosh-apps
Watch
9
0
Fork
You've already forked mokosh-apps
 0
Code Issues Pull requests 1 Projects Releases 14 Packages Wiki Activity Actions

feat(empty-states): use three-part EmptyState for filtered-empty lists #266

Merged
vas2000-work merged 1 commit from feat/mapps-266-standardize-list-empty-states into main 2026-06-17 23:54:51 +02:00
Conversation 0 Commits 1 Files changed 5 +24 -6
David commented 2026-06-17 23:12:46 +02:00
Owner
Copy link

Six primary list pages (companies, contacts, invoices, contracts, articles, audit entries) rendered their filtered-empty branch with a bare single-line message: while their no-data branch already used the rich title/description/CTA EmptyState. This left filtered-empty states inconsistent with the PMS-354 three-part pattern established in tickets.rs.

Each filtered-empty branch now renders the three-part EmptyState (title + description guiding the user back to the filters), matching the tickets.rs reference. No-data branches keep their distinct copy and create CTA, so filtered-empty and no-data-empty render visibly distinct copy and actions.

Sub-resource and config tables (line items, related tickets, dependency-gated config rows) keep the sanctioned bare message: per the TableEmpty doc comment.

#MAPPS-266

Six primary list pages (companies, contacts, invoices, contracts, articles, audit entries) rendered their filtered-empty branch with a bare single-line message: while their no-data branch already used the rich title/description/CTA EmptyState. This left filtered-empty states inconsistent with the PMS-354 three-part pattern established in tickets.rs. Each filtered-empty branch now renders the three-part EmptyState (title + description guiding the user back to the filters), matching the tickets.rs reference. No-data branches keep their distinct copy and create CTA, so filtered-empty and no-data-empty render visibly distinct copy and actions. Sub-resource and config tables (line items, related tickets, dependency-gated config rows) keep the sanctioned bare message: per the TableEmpty doc comment. #MAPPS-266
feat(empty-states): use three-part EmptyState for filtered-empty lists
All checks were successful
Check / clippy + fmt + tests (pull_request) Successful in 2m35s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
113b7d2492 
Six primary list pages (companies, contacts, invoices, contracts, articles, audit entries) rendered their filtered-empty branch with a bare single-line message: while their no-data branch already used the rich title/description/CTA EmptyState. This left filtered-empty states inconsistent with the PMS-354 three-part pattern established in tickets.rs.

Each filtered-empty branch now renders the three-part EmptyState (title + description guiding the user back to the filters), matching the tickets.rs reference. No-data branches keep their distinct copy and create CTA, so filtered-empty and no-data-empty render visibly distinct copy and actions.

Sub-resource and config tables (line items, related tickets, dependency-gated config rows) keep the sanctioned bare message: per the TableEmpty doc comment.

#MAPPS-266
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-apps!266
No description provided.