You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the discussion in #51734, we want to introduce a visibleSourceControls api that allows extensions to get a list of currently selected providers and be notified of changes.
The text was updated successfully, but these errors were encountered:
The plan now is to expose an API for this through the git extension by having an event on the git Source Control object that fires when it is selected.
I assume there would also be a corresponding "blur" event. This means that a change in selection wouldn't be an atomic event, but a blur of one control and focus of another. Alternately, instead of separate blur and focus events, there's one change event that fires with a boolean indicating which it is, but selection change is still not atomic. @joaomoreno what did you have in mind for this? And a list of source controls would be exposed through the git extension, correct?
Perhaps I just misunderstood the explanation of the proposal - if it's just to move visibleSourceControls and onDidChangeVisibleSourceControls to the git extension API, then there's no need for the blur event. But I thought it was something like an onDidSelect event on a source control object itself
From the discussion in #51734, we want to introduce a
visibleSourceControls
api that allows extensions to get a list of currently selected providers and be notified of changes.The text was updated successfully, but these errors were encountered: