Prisma

like well you are passing info, so you shouldn't have to, but the way yours works is different than mine, mine would be like ctx.db.prisma.user, to use prisma binding which accepts info

Screenshot 2019-04-21 at 00.33.28.png

I ask for the `url` subfield for `profilePicture` already in the query I posted.

So strange. To me it all looks legit :man-shrugging::skin-tone-6:

Fixed it. Had to add a field resolver for `profilePicture` under `User`

```
      User: {
        posts: parent =&gt; prisma.user({ id: parent.id }).posts(),
        following: parent =&gt; prisma.user({ id: parent.id }).following(),
        followers: parent =&gt; prisma.user({ id: parent.id }).followers(),
        likes: parent =&gt; prisma.user({ id: parent.id }).likes(),
        comments: parent =&gt; prisma.user({ id: parent.id }).comments(),
        profilePicture: parent =&gt; prisma.user({ id: parent.id }).profilePicture()
      },
```

So the last line. I’ve had to do this before for related field like `posts` `comments` etc but didn’t think I would have to do this for field with no relation whatsoever