angular-cli suggests a command-line interface. However, we intend this tool will also serve as the backend for IDE/editor frontends which create or update your angular project. This could cause some confusion, or vendors may hesitate to use it for that purpose.
I think we should either:
- pick a neutral name for this project, like 'angular-tool' or something better
- split this project into a thin CLI frontend, and a separate backend which can be reused by vendors
I prefer the latter as it's extra-explicit, but it might cause us more work/releases.
angular-cli suggests a command-line interface. However, we intend this tool will also serve as the backend for IDE/editor frontends which create or update your angular project. This could cause some confusion, or vendors may hesitate to use it for that purpose.
I think we should either:
I prefer the latter as it's extra-explicit, but it might cause us more work/releases.