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

angular.json support or custom path parameter to tsconfig.json #1667

Closed
1 of 2 tasks
Viapatis opened this issue May 18, 2022 · 2 comments
Closed
1 of 2 tasks

angular.json support or custom path parameter to tsconfig.json #1667

Viapatis opened this issue May 18, 2022 · 2 comments
Labels

Comments

@Viapatis
Copy link

🚀 feature request

Description

My project has angular.json with given path for tsconfig

{
...
  "projects": {
    ...
    "frontend": {
      ...
      "architect": {
        ...
        "build": {
          ...
            "tsConfig": "src/tsconfig.app.json",
        }
      }
    }
  },
}

since the extension requires sctrictTamplate:true for full-fledged work, which is already enabled in src/tsconfig.app.json , I would not want to write it in tsconfig.json , it bothers me there

Feature Type

What does this bug affect

  • Angular Language Service VSCode extension
  • Angular Language Service server

Describe the solution you'd like

add angular.json support

Describe alternatives you've considered

add path parameter to tsconfig in extension settings

@atscott
Copy link
Collaborator

atscott commented May 18, 2022

I would not want to write it in tsconfig.json , it bothers me there

What exactly do you mean by this? Do you mean you just don't like seeing it in the tsconfig.json? Or that by doing so, you get compilation errors that you cannot resolve? In the v14 release, there is an option to enable strict templates for the extension and ignoring what you have set in the tsconfig.json. Would that work for you?

@atscott atscott closed this as not planned Won't fix, can't repro, duplicate, stale May 20, 2022
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants