feat: remove PRISMA_FMT_BINARY references - #4292
Conversation
|
This PR changes the following pages (Vercel Preview Deploy links): Changed Vercel links
(Note that links will only be valid after Vercel preview deploy succeeded) |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Note: @Jolg42 and I had a doubt about specifying the behavior of |
|
Where did the documentation of the env var move for users of older Prisma versions? |
|
The other PR https://github.com/prisma/docs/pull/4495/files for INtrospection Engine also updates some |
| - The Introspection Engine is served by the Migration Engine from [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0). Therefore, the `PRISMA_INTROSPECTION_ENGINE` environment variable will not be used. | ||
|
|
||
| </Admonition> | ||
| ### CLI Binary Targets |
There was a problem hiding this comment.
Why move this headline up here? PRISMA_FMT_BINARY has nothing to do with "CLI Binary Targets".
There was a problem hiding this comment.
I must have made a mistake when applying the feedback. I'll make the change in another PR.
| PRISMA_INTROSPECTION_ENGINE_BINARY=custom/my-introspection-engine-unix | ||
| ``` | ||
|
|
||
| <Admonition type="warning"> |
There was a problem hiding this comment.
Why remove this unrelated admonition about a different env var? The fmt change does not invalidate this.
DO NOT MERGE UNTIL
prisma@4.10.0is ready to be released.Describe this PR
Follow-up for prisma/orm#16923.
We've stopped using the
prisma-fmtformatter binary inprisma@4.3.0. Although we're currently still downloading the binary, we're no longer using it. As a result,PRISMA_FMT_BINARYhas been a useless environment variable for months.Changes
Remove references to
PRISMA_FMT_BINARY.What issue does this fix?
Contributes to prisma/orm#16924