-
Notifications
You must be signed in to change notification settings - Fork 77
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
feat(frontend): add errors filter and minor fixes for Analyzer results #2731
Conversation
b7a1b61
to
1454674
Compare
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.
Hey @jorgeepc gj my dude, I left a comment about the filtering, let me know what you think!
@@ -6,7 +6,7 @@ interface IProps { | |||
|
|||
const CollapseIcon = ({isCollapsed}: IProps) => { | |||
return ( | |||
<S.CollapseIconContainer>{isCollapsed ? <S.DownCollapseIcon /> : <S.UpCollapseIcon />}</S.CollapseIconContainer> | |||
<S.CollapseIconContainer>{isCollapsed ? <S.UpCollapseIcon /> : <S.DownCollapseIcon />}</S.CollapseIconContainer> |
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.
What haha
|
||
<S.StyledCollapse expandIcon={({isActive = false}) => <CollapseIcon isCollapsed={isActive} />}> | ||
{plugins | ||
.filter(plugin => !onlyErrors || plugin.score < MAX_SCORE) |
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.
Should we consider having a selector or service function that returns only the data we want to render? Instead of having the business logic at the component level?
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.
Yep, good one. Done!
@@ -0,0 +1,25 @@ | |||
import * as S from './AnalyzerScore.styled'; | |||
|
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.
We'll have to move everything to analyzer from linter, bit by bit haha
#2731) * feat(frontend): add errors filter for analyzer results and ux/ui improvements * add analyzer service
#2731) * feat(frontend): add errors filter for analyzer results and ux/ui improvements * add analyzer service
This PR adds multiple UX/UI improvements to the
TraceAnalyzer
result page.Changes
Fixes
Checklist
Loom
https://www.loom.com/share/f56e08c9b6f7490586abfb445d3005fe?sid=ca4367a3-ef43-454f-90e4-6ce80c83117e