Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on Nov 18, 2024. It is now read-only.

Add Navbar actions to summarize all comments - #1170

Merged
kumar303 merged 1 commit into
mozilla:masterfrom
kumar303:summarize-comments-114
Oct 28, 2019
Merged

Add Navbar actions to summarize all comments#1170
kumar303 merged 1 commit into
mozilla:masterfrom
kumar303:summarize-comments-114

Conversation

@kumar303

Copy link
Copy Markdown
Contributor

Fixes #114

Notes

  • This is a quick implementation of enabling reviewers to finish a review. They will have to copy / paste the text but at least it's a start.
  • This is not hidden behind a config flag because comments will never get loaded unless the config flag is enabled.
Example screenshots Screenshot 2019-10-28 13 26 58 Screenshot 2019-10-28 13 27 07

@bobsilverberg bobsilverberg left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really nice, and I love how little code it takes to make this change to the Navbar!

r+wc

)}
<div className={styles.info}>
{currentVersion && (
<div className={styles.infoItem}>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice in the test that you used to check for the text of .${styles.addonName}, which would only include the add-on's name, but now you're checking for the text of .${styles.info} which could include more than the name. I know you're controlling that in the test by making sure there aren't also some comments, but do you think there is any value in still assigning a unique className to this div? I'm not sure there is, but figured I'd raise it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I try to avoid adding class names purely for testing so that's my one hesitation. If we ever show the comments navbar for zero or undefined comments then this test would break but we could cross this bridge when we come to it.

@kumar303

Copy link
Copy Markdown
Contributor Author

I love how little code it takes to make this change to the Navbar!

Heh, well, there were a lot of patches leading up to it.

Thanks for the quick review.

@kumar303
kumar303 merged commit 575220a into mozilla:master Oct 28, 2019
@kumar303
kumar303 deleted the summarize-comments-114 branch October 28, 2019 22:10
@bobsilverberg

Copy link
Copy Markdown
Contributor

I love how little code it takes to make this change to the Navbar!

Heh, well, there were a lot of patches leading up to it.

Thanks for the quick review.

I didn't mean to imply that you didn't do a ton of work leading up to this - I know that's why the patch was so small. I was trying to compliment you on that fact. 👍

@kumar303

Copy link
Copy Markdown
Contributor Author

Oh, I know. I was just trying to say that it wasn't a small patch, unfortunately! React / Redux requires a lot of code and that's something I've been thinking about lately.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prepare to send review comments to a developer

2 participants