v1 compatible version

[lstwn]

Hey guys,

as much as I am looking forward to using Prisma 2 and especially the new datamodel since it includes much needed features, I am a bit aghast about the way the transition is handled.

Let's be honest, Prisma 2 is not even a mature thing yet and production-readiness is also a thing for the future. Right now we have .prisma files in the v1 schema and are definitely stuck with them for a while, but since you are updating this plugin to match the v2 schema already, wouldn't it be nice to leave a v1-compatible version out here?

[Badyl1g]

I completely agree, I read that Prisma 1 would be maintained without breaking changes, and now there's no way to have syntax highlighting for v.1 datamodel

[cmoses8626]

Totally agree. My .prisma v1 file looks FUBAR'd now. Could you guys release a v1 plugin? While Prisma 2 looks exciting, I don't have time right now to do any upgrades, and can't right now anyways as it's not yet production ready.

[mariobermudezjr]

I have a temporary solution:

In your prisma.yml file change datamodel.prisma to datamodel.graphql

and finally change your datamodel.prisma filename to datamodel.graphql

whalaaa!

[sejr]

Yeah, this is extremely frustrating. @ejoebstl @schickling @matthewmueller any thoughts?

[schickling]

Thanks a lot for all of your feedback. I agree we should have come up with a better solution in regards to compatibility and we'll make sure to handle situations like these more thoughtfully in the future. 🙏

While there are currently no plans to release a Prisma 1 compatible version of this VSCode Plugin (for capacity reasons – PRs welcome!), I suggest to go with the workaround @mariobermudezjr has suggested.

[schickling]

Keeping this issue open in case some one wants to submit a PR that adds backwards compatibility.

[nealoke]

Is it possible to just create another plugin for v1? Now all projects in which we use v1 can no longer use the handy plugin.

Nevermind, you can install an older version of a VS code extension

[thebiglabasky]

Hi,
I wanted to chime in since we've released Prisma 2 in GA in June, and propose upgrade guides in our docs.
We don't have plans to provide backwards compatibility but hope upgrading to Prisma 2 will enable more flexibility and control.
I'll thus close this issue.
Thanks!