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
Is your feature request related to a problem? Please describe.
While you have multiple Angular projects in the same vscode workspace it will choose one of the project's version to use it as base, which is problematic if you have multiple different versions.
🚀 feature request
Description
It seems that currently there's no way to choose a specific version to be used and you need to rely on the version detection to find the correct version for the project, but that may not be possible in some edge cases, e.g. the multiple Angular projects in the workspace as mentioned above.
Feature Type
What does this bug affect
Angular Language Service VSCode extension
Angular Language Service server
Describe the solution you'd like
Either provide a way to specify a specific version in the extension's settings or have the manual detection detect all the different Angular versions and ask the user to pick one.
Describe alternatives you've considered
The only workaround at the moment seems to be not using the workspace, or at least not have multiple versions of Angular in the same workspace.
188599
changed the title
Provide a way to specify which the version of Angular to be used
Provide a way to specify which Angular version is used
Nov 21, 2024
Is your feature request related to a problem? Please describe.
While you have multiple Angular projects in the same vscode workspace it will choose one of the project's version to use it as base, which is problematic if you have multiple different versions.
🚀 feature request
Description
It seems that currently there's no way to choose a specific version to be used and you need to rely on the version detection to find the correct version for the project, but that may not be possible in some edge cases, e.g. the multiple Angular projects in the workspace as mentioned above.
Feature Type
What does this bug affect
Describe the solution you'd like
Either provide a way to specify a specific version in the extension's settings or have the manual detection detect all the different Angular versions and ask the user to pick one.
Describe alternatives you've considered
The only workaround at the moment seems to be not using the workspace, or at least not have multiple versions of Angular in the same workspace.
Anything else relevant?
Just to mention here that other people seem to have ran into this same problem.
The text was updated successfully, but these errors were encountered: