ameistad
04/30/2018, 7:51 PMtheom
04/30/2018, 7:51 PMquery allPostsCommentsQuery {
allPostses (orderBy: createdAt_ASC) {
aggregate {
count
}
__typename
id
displaysrc
caption
likes
comments (orderBy: createdAt_DESC) {
__typename
id
posts {
__typename
id
}
text
user
deleted
}
}
}
Jonathan
04/30/2018, 8:22 PMjohhansantana
04/30/2018, 8:54 PMschema.graphql
?
For example, here I want to say that I need the ids
of the images.ldittmar2
04/30/2018, 8:56 PMAndreeo D.GonzĂĄlez
04/30/2018, 9:26 PMAndreeo D.GonzĂĄlez
04/30/2018, 9:27 PMmedelman
04/30/2018, 9:42 PMuser
04/30/2018, 9:42 PMuser
04/30/2018, 9:56 PMuser
04/30/2018, 9:56 PMuser
04/30/2018, 9:57 PMuser
04/30/2018, 10:01 PMuser
04/30/2018, 10:15 PMcoherent
05/01/2018, 3:29 AMunexpected token I in JSON at position 0
kind of error so I know my errors aren't being thrown right.vutran
05/01/2018, 6:37 AMERROR: Whoops. Looks like an internal server error. Please contact us from the Console (<https://console.graph.cool>) or via email (support@graph.cool) and include your Request ID: XXXXXXXXXXXXXXXXXXXX
{
"data": {
"push": null
},
"errors": [
{
"message": "Whoops. Looks like an internal server error. Please contact us from the Console (<https://console.graph.cool>) or via email (support@graph.cool) and include your Request ID: XXXXXXXXXXXXXXXXXXXX",
"requestId": "XXXXXXXXXXXXXXXXXXXX",
"path": [
"push"
],
"locations": [
{
"line": 2,
"column": 9
}
]
}
],
"status": 200
}
I tried pushing to one of my services but it is producing this error.douglaseggleton
05/01/2018, 7:41 AMconst logMiddleware: any = async (
resolve: any,
parent: any,
args: any,
ctx: any,
info: any): Promise<any> => {
<http://logger.info|logger.info>(info);
return resolve();
};
export const server: GraphQLServer = new GraphQLServer({
schema: schema,
middlewares: [logMiddleware]
});
Kyle Gammon
05/01/2018, 7:45 AMrein
05/01/2018, 8:49 AMpicosam
05/01/2018, 9:36 AMgraphql prepare
not regenerating (or modifying to add field) the prisma.graphql
file properly after prisma deploy
?picosam
05/01/2018, 9:37 AMhooks:
post-deploy:
- graphql get-schema --project prisma
- graphql prepare
in my prisma.yml
fileMaxime Scibetta
05/01/2018, 9:42 AM$ prisma deploy
Deploying service `s-cool` to stage `dev` to server `prisma-eu1` !
ERROR: The provided name: coursesByDriver is not a valid name for a relation. It can only have up to 54 characters and must have the shape [A-Z][a-zA-Z0-9]*
{
"data": {
"deploy": null
},
"errors": [
{
"locations": [
{
"line": 2,
"column": 9
}
],
"path": [
"deploy"
],
"code": 4004,
"message": "The provided name: coursesByDriver is not a valid name for a relation. It can only have up to 54 characters and must have the shape [A-Z][a-zA-Z0-9]*",
"requestId": "eu1:cluster:cjgnhh5ufpnuy0b18lwcu1nvf"
}
],
"status": 200
}
Get in touch if you need help: <https://www.graph.cool/forum>
To get more detailed output, run $ export DEBUG="*"
Rory Kelly
05/01/2018, 10:10 AMRory Kelly
05/01/2018, 10:11 AMngeru
05/01/2018, 11:19 AMngeru
05/01/2018, 11:21 AMrein
05/01/2018, 1:16 PMweakky
05/01/2018, 1:42 PM_typeMeta
field available on GCF, which was replaced by aggregate
now on Prisma. The thing is, when you had a one-to-many relationship, that _typeMeta
was available inside the âmanyâ relationship, allowing to query how many items were linked to that type. As instance, letâs say I have a Brand
type and a Product
type, linked by a one-to-many. We used to be able to query something like allBrands { id _productsMeta }
, allowing for instance, to prevent from deleting a Brand
that had `Product`s linked to it if _productsMeta > 0
. How are we supposed to do the same with Prisma ?Maxime Scibetta
05/01/2018, 1:55 PMArvind
05/01/2018, 2:52 PM