-
Notifications
You must be signed in to change notification settings - Fork 45
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
On Windows, the gentimeSettings
are written broken to the file because of endent
#50
Comments
gentimeSettings
are wrongly witten to the file because of endent
gentimeSettings
are written broken to the file because of endent
Quickly looking https://github.com/indentjs/endent/blob/master/src/index.ts I see a lot of potential for not handling |
But now tamino-martinius/node-ts-dedent#21 fun fun. |
endent uses dedent https://github.com/indentjs/endent/blob/master/src/index.ts#L58 dedent does this https://github.com/dmnd/dedent/blob/master/dedent.js#L49 that is the bug My solution was to remove that LOC Doing so did not break the endent test suite (4 tests...) It also did not break the NP test suite (more tests, a few dozen) So there we go, YAL (yet another library) called this time |
In #49 unexpectedly the Windows tests fail. Turns out the test project is using an
output
for the Prisma Clientgenerator
which now would be used (correctly) - and for some reason that path is wrong/invalid.After some local reproduction I found this in
.yalc\nexus-prisma\dist\runtime\index.js
:Investigation: #49 (comment)
End result: There seems to be unexpected behavior coming from
endent
that is used to format that output.Reproduction:
You will get the following output:
vs. expected
The text was updated successfully, but these errors were encountered: