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
{{ message }}
This repository has been archived by the owner on Jan 31, 2023. It is now read-only.
Current code will always connect after importing nodes to an existing environment, because fromAddEnvironment will always be false and at that point environmentRegistryEntry will always exist:
if (!fromAddEnvironment && environmentRegistryEntry) {
// only do this if we run the command from the tree as need to refresh the tree to do setup
await vscode.commands.executeCommand(ExtensionCommands.CONNECT_TO_ENVIRONMENT, environmentRegistryEntry);
}
We should only be refreshing if we are connected to the environment we want to refresh.
The text was updated successfully, but these errors were encountered:
Updated so that the environment view will only refresh if you update the environment you are connected to
closes#1762
Signed-off-by: Caroline Fletcher <cazfletch@gmail.com>
Co-authored-by: Jake <Jakeeyturner@users.noreply.github.com>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current code will always connect after importing nodes to an existing environment, because fromAddEnvironment will always be false and at that point environmentRegistryEntry will always exist:
We should only be refreshing if we are connected to the environment we want to refresh.
The text was updated successfully, but these errors were encountered: