-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add additional Analysis Methods #11994
base: main
Are you sure you want to change the base?
Conversation
How about extracting entity row into its own component? |
Funny you mention it...we have one of those! I can take a look and see how well it would fit together. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great and works well, I don't have any major feedback on the code. I did create a separate ticket for us to refactor the DrawerReportPage
in the future, so this might be a good case for it --- separating out this type of page as its own thing as you mentioned.
83e2803
Code Climate has analyzed commit 83e2803 and detected 2 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 93.5% (90% is the threshold). This pull request will bring the total coverage in the repository to 96.7% (0.0% change). View more on Code Climate. |
Description
TODO
I welcome feedback on improvements to the code. This initial draft I just wanted to make it work so I could see how big the changes are.
Related ticket(s)
CMDCT-4115
How to test
FIGMA
Deployed URL
Notes
I think this code could be better, and I welcome any suggestions for improvement. Some ideas I had:
DrawerReportPage
component that is specifically for this type of pagePre-review checklist
Pre-merge checklist
Review