Skip to content
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

[CORL-1296] New Comment Count #3149

Merged
merged 3 commits into from Aug 28, 2020
Merged

[CORL-1296] New Comment Count #3149

merged 3 commits into from Aug 28, 2020

Conversation

wyattjoh
Copy link
Collaborator

What does this PR do?

With the NEW_COMMENT_COUNT feature flag, comment streams viewed will record the current comment count. When used in conjunction with count.js, it will show / 5 New when the number of comments exceeds what was previously recorded.

What changes to the GraphQL/Database Schema does this PR introduce?

  • Added FEATURE_FLAG.NEW_COMMENT_COUNT

How do I test this PR?

  1. Enable the NEW_COMMENT_COUNT feature flag.
  2. View comments on a story.
  3. In another browser, add a comment to that story.
  4. In the first browser, view the comment count widget and notice the new / 1 New added to the comment count text.

@wyattjoh wyattjoh added this to the v6.4.0 milestone Aug 27, 2020
@nick-funk
Copy link
Contributor

I am only seeing the 2 comments / 1 new counter update if I refresh the page. Is this expected behaviour?

@@ -6,7 +6,7 @@ import { LanguageCode } from "coral-common/helpers";
import {
GiphyGifRetrieveResponse,
GiphyGifSearchResponse,
} from "coral-common/rest/external/giphy";
} from "coral-common/types/giphy";
Copy link
Contributor

Choose a reason for hiding this comment

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

Why were Giphy files modified in this PR?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I moved types around to keep things consistent!

@wyattjoh wyattjoh added the 🚀 merge it! Pull requests that should be merged after status checks pass with a review label Aug 28, 2020
@kodiakhq kodiakhq bot removed the 🚀 merge it! Pull requests that should be merged after status checks pass with a review label Aug 28, 2020
@kodiakhq
Copy link
Contributor

kodiakhq bot commented Aug 28, 2020

This PR currently has a merge conflict. Please resolve this and then re-add the 🚀 merge it! label.

@wyattjoh wyattjoh modified the milestones: v6.4.0, v6.3.5 Aug 28, 2020
@wyattjoh wyattjoh added the 🚀 merge it! Pull requests that should be merged after status checks pass with a review label Aug 28, 2020
@kodiakhq kodiakhq bot merged commit 5e5f17c into master Aug 28, 2020
@kodiakhq kodiakhq bot deleted the feature/CORL-1296 branch August 28, 2020 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 merge it! Pull requests that should be merged after status checks pass with a review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants