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.

Sign up for GitHub

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: handle multiple tsconfig extends for resolving GraphQLSP plugin entry #386

Merged
merged 2 commits into from
Aug 30, 2024
Merged

fix: handle multiple tsconfig extends for resolving GraphQLSP plugin entry #386

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
392f198
fix: handle multiple tsconfig `extends` for resolving GraphQLSP plugi…
aweber1 Aug 29, 2024
f216c49
added changeset
aweber1 Aug 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
added changeset
  • Loading branch information
@aweber1
aweber1 committed Aug 29, 2024
commit f216c4916d30e5379968ade49827f5068e402748
5 changes: 5 additions & 0 deletions .changeset/fluffy-seahorses-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@gql.tada/internal': patch
---

Update the tsconfig resolver to better handle an array of "extends" values in tsconfig.json files when trying to locate the GraphQLSP plugin entry. Before, if you were using an array for "extends", e.g. `"extends: ["./file1.json", "./file2.json"]`, the first file loaded that did not have a GraphQLSP plugin entry defined would throw an error and prevent subsequent files from being loaded and evaluated. The implemented change now allows for the resolver to continue iterating over `extends` values trying to locate a GraphQLSP plugin entry.
Loading