Please take a look at the following examples from the main page:

Wrong result. Should be array of categories, not posts.

Completely wrong example. The comment means array of posts. The code means array of user profiles. The TS type means array of categories. The result means array of posts. 馃く

Wrong comment. The comment mentions the author property, but the code and the result don't.
Also I think it's time to update the all examples (photon.posts -> prisma.post, etc.).
Thanks a lot for catching those @FluorescentHallucinogen馃檹 I just fixed the responses that you pointed out. As for renaming, we're currently already working on a new website and will leave the current website as is (the banner on top in this case provides the context that Photon.js has been renamed).
@nikolasburk
I just fixed the responses that you pointed out.
The problems are not only with responses, but with TS types too.
Just checked

The TS type should be Profile or something like that, not Category[].
Also id: 1 looks very strange, because IDs in Prisma have the different format.
Using unreal IDs in examples produce funny things like:

The post with ID 54394 was requested, but the post with ID cjnymovv3s3ht0a516fhmria8 was returned.
Wrong examples like this may confuse Prisma newcommers.
we're currently already working on a new website
Hope the new website will use the real demo API with real queries and real responses to avoid things like this, and users will be able to edit and play with any examples right on the website. :wink:
Thanks for spotting this @FluorescentHallucinogen.
These have addressed in the new website documentation.
Most helpful comment
@nikolasburk
The problems are not only with responses, but with TS types too.
Just checked
The TS type should be
Profileor something like that, notCategory[].Also
id: 1looks very strange, because IDs in Prisma have the different format.Using unreal IDs in examples produce funny things like:
The post with ID
54394was requested, but the post with IDcjnymovv3s3ht0a516fhmria8was returned.Wrong examples like this may confuse Prisma newcommers.
Hope the new website will use the real demo API with real queries and real responses to avoid things like this, and users will be able to edit and play with any examples right on the website. :wink: