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 Aug 31, 2021. It is now read-only.
Currently it is not being verbose enough about actions being taken, e.g. preparing files, connecting, listing files etc.
Actual behavior
e.g.
When you click on deploy, there will be a long period of silence. (I assume it is preparing the files)
then you have to wait for the pop up to know whether deploy started, or whether you clicked deploy on the right target.
Expected behavior
It should display "Preparing Files", or "Preparing to deploy to ${host}" so we know something is happening and whether we have correctly selected the target.
Adittional Comment
Since this is a deploy plugin, it should be rated as "mission critical" to show everything that is happening between vscode, vscode-deploy-reloaded and the target server.
Thanks for the awesome plugin, so much potential!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Currently it is not being verbose enough about actions being taken, e.g. preparing files, connecting, listing files etc.
Actual behavior
e.g.
When you click on deploy, there will be a long period of silence. (I assume it is preparing the files)
then you have to wait for the pop up to know whether deploy started, or whether you clicked deploy on the right target.
Expected behavior
It should display "Preparing Files", or "Preparing to deploy to ${host}" so we know something is happening and whether we have correctly selected the target.
Adittional Comment
Since this is a deploy plugin, it should be rated as "mission critical" to show everything that is happening between vscode, vscode-deploy-reloaded and the target server.
Thanks for the awesome plugin, so much potential!
The text was updated successfully, but these errors were encountered: