[Issue #8863] Improve Application breadcrumbs#9027
Conversation
|
I might need help with this one. IDK why this has broken the |
@andycochran The Breadcrumb component relies on ReturnToGrantsNotification component, which assumes that searchParams exists in next's navigation. I wouldn't cut that deep though, I'd recommend creating a mock for the Breadcrumb component in the applications test file and adding a test that you are getting the parameters you expect. You can see an example of how to do the mock here and here is where the test of breadcrumb values for that page exists @doug-s-nava Since breadcrumbs are such a core component, it might be worth building some utilities around these mocks so the code doesn't have to be copied everywhere. |
Summary
Fixes #8863
Changes proposed
Context for reviewers
Per new guidance, all breadcrumbs are to be managed consistently, i.e. on their page (not in the constant file). This is part of a larger effort to refactor breadcrumbs. In a subsequent ticket, all Applications pages & subpages will be moved under
/workspace. But that'll happen along with other route changes, when/dashboardwill also change to/workspace.Validation steps
/applications