-
Notifications
You must be signed in to change notification settings - Fork 12
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
Link Terminal with Angular Project #95
Comments
@rubensa As much as I know thats what it already does. However, there could be more then 1 Terminal/Project, since commands like "ng serve" run until you stop them. So to execute "ng generate" while "ng serve" is running, it needs to open a new Terminal. |
Hello @Springrbua I missed that cause Terminal used to create the project is not re-used (so a bit more "reuse" could be done). I've just checked that if I run twice "Run As --> ng build", same Terminal is used. Thanks! |
The Terminal used to create the project probably isn't linked to the Project. We might need to check that. |
Additional info on this issue... NOTE: PATH variable is updated to last created project. |
Thank you for the information. |
Hello Another issue on these is that Terminal should not be reused if a command is currently running (don't know if It's possible to ask the Terminal if there is a running process active). Currently if a process is running you can see the new command written on the terminal (for example ng build) but It's never really run (cause there is an ongoing running process -for example if you previously manually executed an ng server). |
I think that there should be one Terminal linked with one Angular Project.
When you execute a command on a project (Right click, Run as, ng build for example) and there is currently a linked Terminal opened (for previous command run), reuse.
If there is no one (never opened or just closed), create a new one and link with the project (for future re-use).
The text was updated successfully, but these errors were encountered: