Skip to content

Consolidate tree views - #966

Closed
Rachel Macfarlane (RMacfarlane) wants to merge 4 commits into
masterfrom
rmacfarlane/tree-consolidation
Closed

Consolidate tree views#966
Rachel Macfarlane (RMacfarlane) wants to merge 4 commits into
masterfrom
rmacfarlane/tree-consolidation

Conversation

@RMacfarlane

@RMacfarlane Rachel Macfarlane (RMacfarlane) commented Feb 20, 2019

Copy link
Copy Markdown
Contributor

#965

Removes the "Changes in Pull Request" tree view

@RMacfarlane Rachel Macfarlane (RMacfarlane) changed the title remove commented out code Consolidate tree views Feb 20, 2019
@rebornix

Copy link
Copy Markdown
Contributor

The code looks good in overall (I'll take detailed review later) but it seems we didn't handle restoring from review mode when first launch. For example, we checkout to a branch and start reviews, and then reload the window, navigate to the GitHub viewlet, all trees are collapsed. It requries two expands at least (expand category first, find the pr with checkmark if it's not on the second page, expand that pr) to review the code changes again.

public activeFileChanges?: GitFileChange[];
public activeOutdatedFileChanges?: GitFileChange[];
public activeComments?: Comment[];
private _credentialStore: CredentialStore;

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.

Not a fan of having view info in PullRequestManager. We can probably keep the information in prsTreeDataProvider. The ReviewManager takes care of git status change, and modifying PullRequestManager.activePullRequest, prsTreeDataProvider then listens to activePullRequest change event and reveal/refresh the tree when necessary.

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