zonofthor
06/21/2018, 9:26 AMisVisible: !isVisible
sweekar
06/21/2018, 9:54 AMsweekar
06/21/2018, 9:54 AMException in thread "main" org.postgresql.util.PSQLException: ERROR: permission denied for database db_ltr_stg
Darryl
06/21/2018, 10:07 AMDarryl
06/21/2018, 10:07 AMGraphQL server is running on <http://localhost:4000>
{ name: 'New Recipe',
ingredients:
[ { name: 'Ingredient 1', quantity: '1' },
{ name: 'Ingredient 2', quantity: '2' } ],
instructions: [ 'Step 1', 'Step 2' ],
categories: [ { name: 'SNACK' }, { name: 'DINNER' } ] }
Error: Variable "$_v0_data" got invalid value {"name":"New Recipe","ingredients":[{"name":"Ingredient 1","quantity":"1"},{"name":"Ingredient 2","quantity":"2"}],"instructions":["Step 1","Step 2"],"categories":[{"name":"SNACK"},{"name":"DINNER"}]}; Field "0" is not defined by type RecipeCreateinstructionsInput at value.instructions.
Variable "$_v0_data" got invalid value {"name":"New Recipe","ingredients":[{"name":"Ingredient 1","quantity":"1"},{"name":"Ingredient 2","quantity":"2"}],"instructions":["Step 1","Step 2"],"categories":[{"name":"SNACK"},{"name":"DINNER"}]}; Field "1" is not defined by type RecipeCreateinstructionsInput at value.instructions.
Variable "$_v0_data" got invalid value {"name":"New Recipe","ingredients":[{"name":"Ingredient 1","quantity":"1"},{"name":"Ingredient 2","quantity":"2"}],"instructions":["Step 1","Step 2"],"categories":[{"name":"SNACK"},{"name":"DINNER"}]}; Field "0" is not defined by type IngredientCreateManyInput at value.ingredients.
Variable "$_v0_data" got invalid value {"name":"New Recipe","ingredients":[{"name":"Ingredient 1","quantity":"1"},{"name":"Ingredient 2","quantity":"2"}],"instructions":["Step 1","Step 2"],"categories":[{"name":"SNACK"},{"name":"DINNER"}]}; Field "1" is not defined by type IngredientCreateManyInput at value.ingredients.
Variable "$_v0_data" got invalid value {"name":"New Recipe","ingredients":[{"name":"Ingredient 1","quantity":"1"},{"name":"Ingredient 2","quantity":"2"}],"instructions":["Step 1","Step 2"],"categories":[{"name":"SNACK"},{"name":"DINNER"}]}; Field "0" is not defined by type CategoryCreateManyWithoutRecipesInput at value.categories.
Variable "$_v0_data" got invalid value {"name":"New Recipe","ingredients":[{"name":"Ingredient 1","quantity":"1"},{"name":"Ingredient 2","quantity":"2"}],"instructions":["Step 1","Step 2"],"categories":[{"name":"SNACK"},{"name":"DINNER"}]}; Field "1" is not defined by type CategoryCreateManyWithoutRecipesInput at value.categories.
Darryl
06/21/2018, 10:08 AMDarryl
06/21/2018, 10:09 AMRecipeCreateinstructionsInput
(mentioned in the first error) is:
input RecipeCreateinstructionsInput {
set: [String!]
}
Darryl
06/21/2018, 10:16 AMtype Mutation {
...
createRecipe(
name: String!
ingredients: [IngredientInput!]!
instructions: [String!]!
categories: [CategoryInput!]!
): Recipe
}
And the mutation in resolves (index.js):
createRecipe: (_, args, context, info) => {
return context.prisma.mutation.createRecipe(
{
data: {
name: args.name,
ingredients: args.ingredients,
instructions: args.instructions,
categories: args.categories
}
},
info
);
}
sclarsk
06/21/2018, 11:10 AMDarryl
06/21/2018, 11:44 AMalexey.rodionov
06/21/2018, 12:54 PMiamclaytonray
06/21/2018, 2:48 PMwhere
options, even when I want a list of unfiltered objects. Is this true? posts: [Post!]!
should not need a where
argument. That should be optional but crashes my server because I don’t provide that in my resolverjaybauer
06/21/2018, 3:25 PMWhoops. Looks like an internal server error. Search your cluster logs for request ID: the-id
Running prisma cluster logs
shows “Loading logs from docker…“, a checkmark after a few seconds, then shows “Attaching to” and immediately ends with no error. Most of my mutations/queries work fine. Nothing has changed in my project recently, I had to step away from it for a few weeks and now this problem has arisen when there was none before. I’ve tried nuking my cluster/database a few times now in an attempt to fix it to no avail.Jim
06/21/2018, 3:36 PMJim
06/21/2018, 4:59 PMuser
06/21/2018, 5:00 PMuser
06/21/2018, 5:14 PMArnab
06/21/2018, 5:34 PMgroup_by
behavior? For instance if I have a table of Persons
and Cars
where each car has a owner: Person! @unique
, it is quite easy to list all the cars with their corresponding owners. However, if I want to go the other way around, how would I proceed? Usually in SQL I'd go with group_by
cjjenkinson
06/21/2018, 7:28 PMzbarnes
06/21/2018, 7:51 PMinput createUserInput {
email: String!
password: String!
role: String
}
type Mutation {
createUser(input: createUserInput!): User!
}
zbarnes
06/21/2018, 7:52 PMzbarnes
06/21/2018, 7:52 PMemail: String! @constraint(type: "email")
Arnab
06/21/2018, 7:57 PMArnab
06/21/2018, 7:59 PMThere are a bunch of popular libraries out there like the bloated Joi and the async Yup, but I roll my own 100 LOC solution that plugs directly into redux-form so both client and server can use the same validation schema.
eelke
06/21/2018, 9:48 PMThe age old question: would you rather fight 1 horse-sized duck, or 100 duck-sized horses?
csamu
06/21/2018, 10:29 PMNick
06/21/2018, 11:04 PMKhoa Huynh
06/22/2018, 1:38 AMDukuo
06/22/2018, 5:28 AMtodo-service
that has `Todo`s and `List`s, and `List`s have a field that references a User
type; now here's what confusing to me: should I maintain the full Prisma schema on both services? Or maybe that's where stitching to one api-service
comes to play? I know there's nothing written in stone here, but i'm trying to figure out how to properly decouple everything neatly 😛nick
06/22/2018, 6:31 AM