Skip to content

fix(@schematics/angular): relative tsconfig paths in references #30123

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

Merged
merged 1 commit into from
Apr 17, 2025

Conversation

cexbrayat
Copy link
Member

PR Checklist

Please check to confirm your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

We can't quickly navigate to the referenced paths as VSCode for example thinks they are modules (Failed tor resolve tsconfig.app.json as a module)

What is the new behavior?

This makes them clickable for a quick navigation in IDEs

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

This makes them clickable for a quick navigation in IDEs
@cexbrayat cexbrayat force-pushed the fix/relative-tsconfig branch from e327fe4 to 17eb05a Compare April 17, 2025 13:32
@clydin clydin added target: major This PR is targeted for the next major release action: merge The PR is ready for merge by the caretaker labels Apr 17, 2025
@clydin clydin merged commit 5e8c649 into angular:main Apr 17, 2025
32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: @schematics/angular target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants