-
Notifications
You must be signed in to change notification settings - Fork 214
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
Upgrading to Angular 14 causes Unknown arguments: inlineStyle, inlineTemplate #1302
Comments
If you restart vscode, is the error still reproducible? There's some caching done when initially loading the workspace and if the upgrade happened while vscode was still opened, then we probably still have the old schema loaded. |
yes, what folders do i delete to clear the cache? |
There's no folders, it's in memory cache. That's why restarting clears it. If it didn't work after restarting vscode, I'll take a look today to see if I can reproduce it. |
I believe the new CLI command is --inline-template instead of --inlineTemplate Thank you for all your helpful work on this amazing project. Much appreciated. |
Weird.. I'm not sure where your Do you happen to have angular cli installed globally? And if it is, is it the same version as your local workspace one? |
Projects based on Angular 13 work, but give this warning: Support for camel case arguments has been deprecated and will be removed in a future major version. When I update them to 14 via ng update, then --inlineStyle eg no longer work |
Can you provide a reproduction in a repo I can clone? Nx Console reads the schema.json files in the node_modules folder. If you look into |
Very strange. It shows:
But the CLI's Generate command says that is deprecated now in 14. Support for camel case arguments has been deprecated and will be removed in a future major version. |
That's where we get the information from.. 🤔 Is your angular cli installed globally? |
Yes, 14.0.4 everywhere |
Current Behavior
When using the Generate Component option with inline style and template checkboxes checked the CLI errors out:
Environment
The text was updated successfully, but these errors were encountered: