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
If the project have an amplify folder this means that it is using aws services, try to open all the possible resources like dynamo tables or cloudwatch instances (or the next featyre that this extension will have).
At least on the first run ask if you want to open or create the access point to them in the extension.
The text was updated successfully, but these errors were encountered:
I like the idea but it would require that extension must be activated every time (not just when you click on the logo in the sidebar) and it would need to scan the folder in order to figure out it's an amplify project.
I think it's better to have an "amplify" service just like "serverless framework" which would list all available resources when you activate the extension.
Maybe a button that will check that for you
if there isn't a setting.json yet, you can add your own services or check if there is an amplify folder (one button for each functionality)
This is a big one
If the project have an amplify folder this means that it is using aws services, try to open all the possible resources like dynamo tables or cloudwatch instances (or the next featyre that this extension will have).
At least on the first run ask if you want to open or create the access point to them in the extension.
The text was updated successfully, but these errors were encountered: