[Fix] no-duplicates: type import fixer generates valid TypeScript #2149
Conversation
e5c2ea6 to
7396b1b
Compare
|
@GoodForOneFare are you no longer interested in landing this? |
|
@ljharb would you have otherwise accepted this PR? I'd be happy to open a new PR and see it through, we've been bitten by this before. |
|
@nwalters512 please do not open a new PR - i'd prefer @GoodForOneFare to restore the branch and reopen this one, and i can take your branch and pull it into this PR. I haven't had a chance to review this one, but any fixer that's safe is one I'm always anxious to add. |
|
Sure - how long would you like to wait for @GoodForOneFare to reopen? If they've abandoned it entirely, I would still very much like to get this fix landed. |
|
Hi folks! I only had a short window in which I could contribute, so @nwalters512 can pick this up without stepping on my toes 😸 fwiw, even with this fix, enabling this + |
|
@GoodForOneFare any chance you could restore the branch and reopen the PR? That way @nwalters512 can post a link to a branch and I can pull in the commits, without needing an extra PR. |
|
Done 👍 All yours, @nwalters512! |
|
@nwalters512 please comment with a link to a rebased/updated branch, and i'll pull it in :-) |
…ype imports Co-authored-by: Nathan Walters <nwalters@nerdwallet.com> Co-authored-by: Gord Pearson <gord.pearson@shopify.com>
7396b1b to
712ee49
Compare
no-duplicates: valid default + named types fixerno-duplicates: type import fixer generates valid TypeScript
Fixes #2114, #2130
Note that #2114 suggests the correct fix looks like:
but this PR will generate:
This avoids conflicts with
no-named-defaultmentioned in #2130.