Skip to content

Render resolved conversations differently on description page - #2471

Merged
Rachel Macfarlane (RMacfarlane) merged 1 commit into
masterfrom
rmacfarlane/resolvedConversations
Feb 8, 2021
Merged

Render resolved conversations differently on description page#2471
Rachel Macfarlane (RMacfarlane) merged 1 commit into
masterfrom
rmacfarlane/resolvedConversations

Conversation

@RMacfarlane

@RMacfarlane Rachel Macfarlane (RMacfarlane) commented Feb 5, 2021

Copy link
Copy Markdown
Contributor

Fetch whether review threads are resolved, and show them collapsed on the description page.
Screen Shot 2021-02-05 at 12 00 45 PM

Screen Shot 2021-02-05 at 12 00 52 PM

First part of #339

Comment thread src/github/utils.ts
}

export function parseGraphQLComment(comment: GraphQL.ReviewComment): IComment {
export function parseGraphQLComment(comment: GraphQL.ReviewComment, isResolved: boolean): IComment {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why not update GraphQL.ReviewComment to include the resolved property so that you don't have to pass it as an additional param here?

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.

The property is actually at the thread level instead of on individual comments, but I thought adding a concept of threads instead of the comments we use everywhere was too big of a refactoring

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants