-
Notifications
You must be signed in to change notification settings - Fork 123
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
Please add support for latest V19-Next #2095
Comments
should be done |
@188599 potentially you have a workspace with multiple Angular versions in your project? consider clicking on VSCode's |
Yes, that is the case. I'm migrating a very old Angular project and I have both the old one and the new one in the same workspace. The language service is pulling the version from the old project in this case. |
Ah yeah, that's a known limitation of the version detection we have. I don't know if there is a tracking issue for this somewhere. |
Is there a way to force a specific version to be used instead? |
Can you create a feature request for this? I think this is a good suggestion |
Created this one #2118 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Is your feature request related to a problem? Please describe.
Latest V19 builds have now standalone:true as default.
This makes the angular language service show errors in VSCode when using the imports array in a component.:
imports is only valid on a components that is standalone
🚀 feature request
Description
Add support for standalone: true as default (ie. allow imports array)
The text was updated successfully, but these errors were encountered: