improve: avoid conflict import paths for Twoslash #1069
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jasonkuhrt
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR works around an issue wherein graffle package imports conflict with generated client imports with Twoslash. More details here: twoslashes/twoslash#54.
The generated client now has all modules nested into
<generated dir>/modulesso that Twoslash does not find modules in./graffle/*that matchgraffle/*.One potential remaining issue though is that we may intentionally want to have symmetry between
./<generated>/*andgraffle/*as we further develop Graffle, in which case we'll be unable to "avoid" this issue.