Skip to content
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

Configuration for "only" project AngularCLI #94

Open
rubensa opened this issue Jul 7, 2017 · 6 comments
Open

Configuration for "only" project AngularCLI #94

rubensa opened this issue Jul 7, 2017 · 6 comments
Milestone

Comments

@rubensa
Copy link

rubensa commented Jul 7, 2017

If you want to "only" use the project instance of AngularCLI (ng command) by "always" setting the install option when creating a new Angular Project, and then you access AngularCLI preferences (Preferences --> JavaScript --> TypeScript --> Angular --> CLI) you get an error message when trying to leave preferences page.

If you keep the default "ng configuration" as "Use ng global installation" and you don't have a global ng installed (as is my case) you get an:

The currently displayed page contains invalid values.

error message that prevents you from leaving the page.

If you change the option to "Use ng custom installation" and select the default value of "${project_loc:node_modules/.bin}" you get the same error message that prevents you from leaving.

The only way to leave the preferences page is by pressing Cancel button (despite you have or have not touched anything).

@probert94
Copy link
Contributor

I guess you are trying to configure the global preferences, not the project specific preferences right?
In that case, you are right. It is impossible to store project-specific paths, since there is currently no project.
The global preferences page should probably not validate the ng installation path.
However, you can now choose the ng location during the project-creation, by simply selecting "install angular-cli".

@rubensa
Copy link
Author

rubensa commented Jul 10, 2017

Yes, that's what I was doing.

The global preferences page should probably not validate the ng installation path.

Probably that should be the best option for now (or only show a warning, not an error; if that's possible).

@probert94
Copy link
Contributor

But I guess, the Project-Creation WIzard should be customized again to be able to use the global configuration.
For the moment you can only select "global CLI" and "install CLI". There is no option "use global preferences".
So the global settings won't matter for a newly created CLI-Project, at least for the moment.

@angelozerr
Copy link
Owner

@Springrbua can we close this issue?

@angelozerr angelozerr added this to the 1.4.0 milestone Nov 7, 2017
@probert94
Copy link
Contributor

Yea I think we can close this.
If there are any issues with the new preferences, we should open a new issue

@ronatartifact
Copy link
Contributor

Does this require an update to the documentation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants