-
Notifications
You must be signed in to change notification settings - Fork 68
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
added info link for Plugin Health Score #1331
added info link for Plugin Health Score #1331
Conversation
Solved #1328 |
acb8196
to
1cf152e
Compare
Please don't mark comments as resolved when they are not.
is still to address. I'd recommend keeping the question mark clickable, additionally to the hover. |
It is clickable and also can be hovered |
Why do you think so? You removed the logic for that, after my previous comment, for no reason. |
I didn't mention the tooltip, I mentioned the linking action you previously had on the question mark. The need to hover first and click later just requires more action of the user, when there's no need for it. |
O.. I misunderstood what you said before, but now I get it. What I have done is I have removed link from "?" and added What needs to be done is I have to add |
Yeah, I questioned the "why". This design causes more noise for the end user, especially if the hover is not sticky, if you're not fast quick, you don't make it: Kapture.2023-04-13.at.09.10.31.mp4 |
Noted... With all fixes, I will push the next commit |
just now checked the code its reactstrap tooltip component causing that issue of hover, tested some changes but still result remains the same, so should I remove the tooltip component and rewrite a different code for it? |
None of that is needed, and out of the scope of the PR. All I asked for is re-adding the ability to click the question mark. |
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.
Thanks!
@@ -24,6 +57,7 @@ PluginHealthScore.propTypes = { | |||
healthScore: PropTypes.shape({ | |||
value: PropTypes.number, |
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.
value: PropTypes.number, | |
value: PropTypes.number.isRequired, |
@@ -24,6 +57,7 @@ PluginHealthScore.propTypes = { | |||
healthScore: PropTypes.shape({ | |||
value: PropTypes.number, | |||
}), | |||
name: PropTypes.string, |
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.
you don't handle name not being provided, so it should be required
name: PropTypes.string, | |
name: PropTypes.string.isRequired, |
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.
@Harsh3341 do you want to do a followup pr with these? I'm just going to merge.
#1320 (comment)
Info links for plugins is been added