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
Adding flags adds unnecessary complexity, especially given the wide variety of code editors available. Each integration would require maintaining specific logic for different editors, which adds overhead and potential for issues. Additionally, when opening an editor, the intent is often to run the command in its terminal.
Command
new
Description
it would be nice if CLI prompts for if we want to open the folder after installation is finished instead of manually opening our editors there.
for bonus point maybe if CLI also asks we would wanna serve the project.
Describe the solution you'd like
maybe something with the prompts itself would be nice that asks if we want to open the folder with [x] editor or serve project after installation.
we could also have flags that we can pass instead of prompting, something like:
ng new [...] --editor=code --auto-serve
Describe alternatives you've considered
maybe write package that takes same commands as Angular CLI and runs them afterwards.
chain commands all the time:
ng new [...] && cd [name] && code . && ng serve --o
The text was updated successfully, but these errors were encountered: