https://www.prisma.io/ logo
Join Slack
Powered by
Also confused as to why all of the links in the do...
# prisma-whats-new
t
Also confused as to why all of the links in the docs referring to the graph cool cli read me link to the Prisma docs
l
Plenty of questions over the pas week or so around this including myself. Basically docs have not been updated, unless you use the Prisma docs (https://www.prismagraphql.com/docs/) which is the way forward.
So the history goes like this. 1) graphcool was renamed graphcool-framework so that they architecturally could split the framework for building a solution from the engine that integrates with a database. 2) then they recycled the graphcool name within the beta program working towards v1 which was the cli to manage the database and its interface (Graphql CRUD) 3) Then when it was time to release v1 of this it was renamed Prisma.
t
Prisma says to use your own database though, I'm looking to not use an existing or own database.
l
The docker version has mysql built in
t
2. Why launch a project with literally all of your docs out of date or just flat out wrong
l
There will be a DB somewhere
Not sure about the lag in keeping the docs up to date, but I suspect the Prisma docs was where they put the effort into
And the old graphcool docs were not updated in time to reflect.
As an outsider I agree it looks erratic and non professional, but the last 6 months graphcool has shifted focus, and done a lot to get this out the door
t
Apollogies for my frustration, but I'm having a tough time making sense of any of this at this point
h
yeah setting this up definitely requires some digging but that's understandable, the project just came out. Hopefully it improves quickly 🙂
t
I just wanted an option that was what Graph.cool was initially offering
l
I totally agree, sticking with prisma and their docs will be the way forward
h
Prisma will be engine for graphcool-framework. Graphcool framework is hosted version with serverless functions etc
l
There will be a fully functional "Prisma Cloud" option that graphcool will manage
The current graphcool console still works, though I use it without auth and functions until I am ready to switch over to Prisma
t
I've been told by multiple people that the graphcool console should not be used
and that it's legacy
l
For development it is just fine
I wouldn't use it in prod
After all, the API is just graphql as long as you are not doing anything graph.cool specific
t
Honestly between Prisma, Prisma Cloud, Graph Cool, Graphcool Framework, Graph Cool GUI there is no clarity
I'm looking for a service to commit to and it's difficult to commit to a moving target
l
True... and there is also AWS AppSync that is an option also ,but in a slightly different way
Personally, when I get in the Prisma bandwagon, I will want to host Prisma myself and build the API Gateway into my graphql schema myself. Better control and will fit in line with other non graphql features
h
t
I've read the blog post a few times, it doesn't clear up much TBH
h
Its forum post what expalins everything
l
I personally like to watch the short youtube clips. To get the idea
t
You may feel that way, but as someone who's trying to replace the backend as a service tool, the forum post clears up very little
h
So ask your questions on forum and you will get your answers https://gist.github.com/marktani/13a6ac8ac9b87b821fa753480de5b529
t
I came here to ask because I thought that was fine. If it's not, I can surely post on the forum instead. Again, I'm not trying to blame here, but when the docs are so incorrect, it's tough to make sense of it all.
h
If you read forum post you will know why its incorrect
t
...
h
I am trying to help you, thats all
t
Really?
h
Yea, giving you sources of truth
t
Telling me to re-read a forum post again isn't super helpful TBH. I think my confusion is justified given the extreme changes in GraphCool's offerings
People have already told me that the new naming and packages have caused a lot of confusion.
I think improvment to the Prisma docs and landing pages could solve many of these issues.
You can discount my thoughts on this and tell me to post in the forums or re-read a post or you can try to understand why this is all confusing and improve the product.
Thanks for your help @lancej
n
@ToraRTC I fully agree with you and I'm sorry for all the confusion. I was unavailable today to fully address it, in Slack and our chat. I will make sure to do this tomorrow 🙂 Thanks so so much for providing your feedback, this means a lot to me!
Please be aware that others participating in this discussion are not part of the core team, and I'm convinced they are genuinely trying to help 🙂 This is up to me however, and I hope I can do so tomorrow.
t
No worries. I hope I'm not being unreasonable. I honestly have spent some serious time trying to make sense of it all after first using the GUI.
s
just my 2 cents: I fully appreciate the effort and tools you've been building, and as a developer myself I understand the major work and focus you've been putting in developing Prisma so I get that there can be some missunderstanding and outdated info. That said I think it would be very beneficial to new and existing users like myself to have a comparison between graphcool and prisma and how they difer, since It took me some hours (as a graphcool and graphql previous user) and some hands on the tools to understand how they relate. It'd be awesome to also have a list of the features you get out of the box, compared to, let's say rolling your own apollo server with something like typeorm. Thanks for your work!
👌 1
t
I think that's dead on. Most of my confusion could have been avoided if there was something like that.
2 Views
Open in Slack
PreviousNext
Powered by