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

fix: tsconfig paths are not expanded correctly for tsconfigs and libs not placed at workspace root #502

Merged
merged 4 commits into from
Aug 14, 2023

Conversation

alexeagle and others added 4 commits August 14, 2023 14:45
Synced from #500 by
joelMuehlena:
fix: tsconfig paths are not expanded correctly for tsconfigs and libs
not placed at workspace root (#499)

---

Fix #499

### Test plan

- Covered by existing test cases
- New test cases added

### General

This fix ensures, that if an expanded import path like specified in the
corresponding tsconfig.json (of a file which for example lays in the
following space <root>/projects/p1) is not absolute e.g. `@org/liba/* ->
./*: @org/liba/test` will be expanded to `projects/p1/test`. Otherwise
gazelle has issues resolving the correct imports.

Closes #500

---------

Co-authored-by: Joel Mühlena <joel.rene@muehlena.de>
GitOrigin-RevId: 57f6b0b18df932cc543d334b4eac1118e70674cf
@alexeagle alexeagle enabled auto-merge (squash) August 14, 2023 21:52
@alexeagle alexeagle changed the title chore(copybara): sync commits from Aspect-internal silo fix: tsconfig paths are not expanded correctly for tsconfigs and libs not placed at workspace root Aug 14, 2023
@alexeagle alexeagle merged commit 691843d into main Aug 14, 2023
6 checks passed
@alexeagle alexeagle deleted the 8AEF12339515D0A47D3EA1E9D42A18D8 branch August 14, 2023 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants