-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amplify environment plugin requires restart of VSCode after pulling new environment #3
Comments
Hi @abdallahshaban557 I think this is possible by also having a filesystem watcher on the team provider file. I will have a look at it |
Awesome! Thank you, Poya! |
I think I have found a solution. I looked at the activation events (specific events that activate the extension). Before this feature request, the extension activation event was an event that looked for a With this fix, the extension is activated at startup, but in a kind of silent mode with a file system watcher subscription. When the file system watcher detects the creation of the This means that when you create a new Amplify project, or pull a project using the CLI, the extension will detect the creation of the Thanks for the feature request, please let me if this fix works for you and what you think. Best Regards! |
Will try this out! Thank you so much, @poyashad! |
Thanks for testing it out @abdallahshaban557 ! I think the extension will have to do some checks and also watch for when the project gets deleted. And go into "silent mode" again. I will take a look at it! |
Since the extension did not detect the deletion of the Thanks! |
Hi @poyashad - I have tried it again, and it seems the issue was not resolved. I am still seeing duplicate environments when I try to remove an Amplify project. |
Hi @abdallahshaban557, i will take a look and try to duplicate the issue! |
Hi @abdallahshaban557 Sorry for the inactivity! Could you please just post the AWS Amplify CLI commands that are triggering this issue? I will try to replicate the problem. |
Hi @poyashad - The command I was using is |
Thanks @abdallahshaban557 i will try to replicate and debug. |
Hi Poya,
I have noticed that after I create a new Amplify project, or pull a project using the CLI, I need to restart VSCode before the plugin starts showing my environment details.
Is this something that can be addressed?
The text was updated successfully, but these errors were encountered: