Javier Diaz
12/11/2017, 1:32 AMGregor
12/11/2017, 1:39 AMGregor
12/11/2017, 1:39 AMGregor
12/11/2017, 2:05 AMgql`{...}`
I wonder if there is a way without using graphql-tag
though?matar15
12/11/2017, 6:05 AMmatar15
12/11/2017, 6:06 AMphil
12/11/2017, 8:17 AMcreatedAt
and updatedAt
default fields? Is there a different directive than @model
that has those (with corresponding date creation/update behaviors)?jovantoskic
12/11/2017, 9:05 AMOleg Galaburda
12/11/2017, 9:43 AMOleg Galaburda
12/11/2017, 9:43 AMAlina
12/11/2017, 10:15 AMAlina
12/11/2017, 10:16 AMAlina
12/11/2017, 10:16 AMLotafak
12/11/2017, 12:10 PMZyad Sherif
12/11/2017, 12:53 PMed
12/11/2017, 1:09 PMlogin/pass
of graphcooled
12/11/2017, 1:09 PMpatrick
12/11/2017, 2:27 PMterrence
12/11/2017, 3:52 PMagartha
12/11/2017, 3:53 PMLotafak
12/11/2017, 3:53 PMtype User @model { ... }
we get allUsers built-in method. Now, when Iām trying to restrict the access to read on this type I made
permissions:
- operation: User.read
authenticated: true
query: url
and in linked file for query field
query ($user_id: ID!) {
SomeUserExists(filter: {id: $user_id})
}
but when any user is logged in I have access to all of the users. How can I rewrite it to achieve that logged in user can see only his data even if quering allUsers?ehodges
12/11/2017, 5:20 PM17 | <Link to=ā/createā className=āml1 no-underline blackā>submit</Link>| ^ 18 | </div> 19 | } 20 | </div>
johhansantana
12/11/2017, 5:38 PMDukuo
12/11/2017, 5:48 PM>>- permissions- operation: Model.operation authenticated: true query: - ./src/common/permissions.graphql:IsSomeUserRole - ./src/model/permissions.graphql:SomethingSpecificToThisModel
Dukuo
12/11/2017, 5:57 PMuser
12/11/2017, 6:55 PMhttps://prisma.slack.com/files/U66MTT41M/F8CBVQKEV/image.pngā¾
user
12/11/2017, 6:56 PMhttps://prisma.slack.com/files/U66MTT41M/F8CBVQKEV/image.pngā¾
user
12/11/2017, 6:56 PMhttps://prisma.slack.com/files/U66MTT41M/F8CBVQKEV/image.pngā¾
Pedro Jardim
12/11/2017, 6:59 PMmattbryanswan
12/11/2017, 7:40 PM