feat: Bump @prisma/prisma-fmt-wasm to 3.8.0.
#54
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 825c573:
|
|
Hey @tomhoule! I can not migrate to 3.8.0 because of this change prisma/prisma-engines#2538, I've tried to pass params as it was done in https://github.com/prisma/language-tools/blob/b2902f66b819b0d2df4a446e2fda5212273278f0/packages/language-server/src/test/format.test.ts#L10-L20 but still no luck, could you please check 🙏 |
|
Hm weird. This is how we use it in the Prisma language server: https://github.com/prisma/language-tools/blob/b2902f66b819b0d2df4a446e2fda5212273278f0/packages/language-server/src/prisma-fmt/format.ts#L4 |
avocadowastaken
changed the title
@prisma/prisma-fmt-wasm to 3.8.0.@prisma/prisma-fmt-wasm to 3.8.0.
avocadowastaken
force-pushed
the
prisma-3.8.0
branch
2 times, most recently
from
c127393 to
c8aaf96
Compare
avocadowastaken
force-pushed
the
prisma-3.8.0
branch
from
c8aaf96 to
825c573
Compare
|
wow, that's unexpected that it was so strict. We use the lsp-types crate so I guess they're strict about spec-compliant inputs. Kudos for figuring this out, sorry for the trouble! |
No description provided.