window.tabs
after vscode.open
command is not up to date
#139786
Labels
api
bug
Issue identified by VS Code Team member as probable bug
insiders-released
Patch has been released in VS Code Insiders
verified
Verification succeeded
workbench-editors
Managing of editor widgets in workbench window
Milestone
I just pushed a test for asserting
vscode.open
command properly applies theViewColumn
argument and my initial idea was to use thewindow.tabs
API for that purpose, but as it turns out, awaitingexecuteCommand
and then callingwindow.tabs
does not work, maybe (?) because of the micro queue that puts the events at the end?Using
window.activeTextEditor.viewColumn
however seems to work, and I wonder if we need to makewindow.tabs
also work so that extensions see a consistent picture.If we don't want to drop the micro task then maybe those commands that leverage editors need to await the tabs model being synced back to the extension host?
//cc @jrieken
The text was updated successfully, but these errors were encountered: