MCR-2553: CMS can navigate to rate review q&a via sidebar

[JasonLin0991]

Summary

MCR-2553

• There is a side nav on the rate review page
• Above the side nav there is a Go to dashboard link that takes the user to the rate dashboard
• Q&A link switches the page to the rate Q&A page with header and an empty Q&A table ( see designs )
• The url for the Q&A view is "https://mc-review.onemac.cms.gov/rates/:id:/question-and-answers".
• There is a "Add question" button, that has no functionality.
• CMS users without a division see a warning banner about division assignments. ( same as contract questions )
• CMS users without a division do not see the “Add questions” buttons
• If a CMS user visits "/submissions/:id:/rate/:rateID/question-and-answers" they are redirected to "/rate/:id/question-and-answers".
• Features implemented in this ticket are behind the qa-by-rates feature flag

Extra work

• Fixed page content shifting when a scroll bar appears
• Fixed background on the settings page to match rest of the pages.

NOTES

• I had to place the redirect in the RateSummartySideNav component instead of AppRoutes. I couldn't figure out how to get the URL params in AppRoutes in order to redirect to the correct rate.
  • Open to other suggestions.

Related issues

Screenshots

Test cases covered

RateQuestionResponse.test.tsx

• 'CMS user tests'
  • 'renders error page if rate revision does not exist'
  • 'renders error page if rate is in draft'
  • 'renders waring banner if CMS user has no assigned division'

RateSummarySideNav.test.tsx

• 'loads sidebar nav with expected links'
• 'renders error page if rate status is DRAFT'
• 'redirects to rate summary Q&A page'

QA guidance

[pearl-truss]

Changes LGTM

[haworku]

@JasonLin0991 I agree this is a little funky, we are setting up the route exclusively just to redirect in the rendered component, it is a little bit of a braintwister

Don't know the solution without pulling down code more, I can take a look though on Monday. Assuming from you PR description comment you tried <Redirect /> already in AppRoutes? Is the correct?

[haworku]

With that said, no blocking, you can merge if you feel ready

[JasonLin0991]

I believe was replaced with . The complication is the difference in the route paths and parameters between submission summary and rate summary. Summary page id param is the contract id where as rate summary it is the rate ID. So we would have had to add more logic in AppRoutes to handle getting the rate ID from the url to generate the redirect path. I decided to put this logic in the RateSummarySideNav since both routes are nested in this outlet.

I think if we refactored how we setup the routes to use createBrowserRouter, maybe loader can do the redirecting.