-
Notifications
You must be signed in to change notification settings - Fork 405
Conversation
Ensure that the Git panel is on the left but is also the one that is active
The builds appear to be failing because atom/atom#14125 hasn't hit stable yet. Will we still need to |
I think the beta failures are related to some test flake that's slipped in. I'll 🔧 those against master. |
}; | ||
} | ||
|
||
@autobind | ||
rerender(callback) { | ||
if (this.workspace.isDestroyed()) { | ||
return; | ||
} |
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.
@smashwilson 🤔 What if the workspace isn't destroyed but the package is deactivated? Something we should handle in these cases?
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.
Good question. I'd hope that potential rerender()
calls would be cleaned up by the CompositeDisposable disposal. But it's well worth a check to see if that's possible.
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.
👍
The first time the package is loaded for a given project, this will show both panels in their default location. The Git panel will be on the left while the GitHub one will be on the right, and the Git panel will be the one that is active.
Fixes #673