GraphQL query "me" get related content

[deeq14]

What is the current behavior?
I am using GraphQL plugin and the query 'me' doesn't have for example a related content by the user, just the basics, id, username, email e.t.c..

for example I have to do this way,

query {
  user(id: "5c38667108f3c10d9fe2981f") {
    articles {
      posts
    }
  }
}

which means I have to allow a user to access /user:_id which also exposes that the user can get other users content!

Steps to reproduce the problem
Create a content add a field and relation to a user and do a query "me" with the related content

Suggested solutions
It will be nice to have a way we can do this

query {
  me {
    articles {
      posts
    }
  }
}

which means a user has access to only his/her content.

[Aurelsicoko]

@deeq14 Thank you for raising this issue! Do you have time to implement it? We'll be happy to merge it to the codebase 👍

[deeq14]

@Aurelsicoko Unfortunately I am just a beginner/intermediate in js and lack of skills may hinder.. but I will try 👍

[Aurelsicoko]

@deeq14 You should start here (https://github.com/strapi/strapi/blob/master/packages/strapi-plugin-users-permissions/config/schema.graphql#L29). But it seems that the query is already implemented, can you confirm?

[lauriejim]

@Aurelsicoko the me Query exist but the topic is about related data of the user.

[deeq14]

@Aurelsicoko I meant to actually get the related content of the user, like lauriejim said.

[Aurelsicoko]

Okay, I got it! If you want to be able to retrieve a relational field through the query me, you have to change this line https://github.com/strapi/strapi/blob/master/packages/strapi-plugin-users-permissions/config/schema.graphql#L25. Instead of returning UsersPermissionsMe, you need to change this line by UsersPermissionsUser.

[yareyaredesuyo]

I had the same issue before, so I changed UserPermissionsMe config file's scheme directly. And it worked.

Edit like this

    type UsersPermissionsMe {
      _id: ID!
      username: String!
      email: String!
      confirmed: Boolean
      blocked: Boolean
      role: UsersPermissionsMeRole
      description: String  // <- add this line (change what you want to add from User scheme. )
    }

But this issue is maybe not documented.

So, the answer is maybe...

1. Add document about how to change UserPermissionsMe scheme.
2. Allow user to edit UsersPermissionsMe from admin panel.

[Aurelsicoko]

The UsersPermissionMe isn't a model and it's only available when you're using GraphQL. So, option 1 is the only option we have.

@yareyaredesuyo can you make a PR and update the documentation, please? Thank you :)