callan
10/27/2018, 11:26 AMArgsCreateItem needs to be given the same index signature, otherwise it cannot be assigned?callan
10/27/2018, 12:52 PMcallan
10/27/2018, 12:52 PMaffanshahid
10/27/2018, 4:35 PMSufyan
10/27/2018, 11:16 PMzonofthor
10/27/2018, 11:26 PMmutation {
  updateStation(
    where: { id: "S8Cdjsc3DsPvuQJp1ZlSMGfej" }
    data: {
      editors: {
        connect: [
          { id: "aZGL8IkcULGPNFdUZG37Qc1kX" }
          { id: "1coBflfBj8prHe4USggSbG49J" }
          { id: "4Kr8VGxMHys3hH5B0pJDighRc" }
          { id: "54lPfOvRAMXljSk7wlJp6r29N" }
        ]
      }
    }
  ) {
    id
    title
    editors {
      id
      name
    }
  }
}hinsxd
10/28/2018, 7:22 AMhinsxd
10/28/2018, 7:23 AMPostType { id name } with prisma, what is the best practice?hinsxd
10/28/2018, 7:25 AMid not custom id setting, so I need to set postTypeId: Int @unique as a workaround, but this just doesnt sounds natural. I want to do something like ordinary CMS.hinsxd
10/28/2018, 7:27 AMIndustrial
10/28/2018, 9:47 AMWhereUniqueInput and why it only takes an id property; https://github.com/prisma/prisma/issues/3384Industrial
10/28/2018, 9:54 AMIndustrial
10/28/2018, 9:54 AMupsertMarket(where) and market(where) are both WhereUniqueInput so I also can not look up a market by anything other then it's ID ...Industrial
10/28/2018, 9:55 AMIWantPizza
10/28/2018, 12:56 PMlucas
10/28/2018, 3:55 PMsamba
10/28/2018, 4:20 PMMojoJojo
10/28/2018, 7:04 PMMojoJojo
10/28/2018, 7:05 PMtype StockItem {
  features(standard: Boolean): [Feature]
}MojoJojo
10/28/2018, 7:05 PMZefex Developer
10/28/2018, 8:25 PMlucas
10/29/2018, 12:57 AMlucas
10/29/2018, 12:57 AMasync getPhoneNumber(parent, args, ctx, info) {
        const phoneNumber = args.phoneNumber
        const result = await ctx.nexmo.verify.request({number: phoneNumber, brand: 'Awesome'},  (err, result) => {
            if(err) {
                throw new Error(err)
            } else {
              console.log(result);
                
              if(result && result.status == '0') {
                  return result
              } else {
                return null
              }
            }
          })
          const token =  jwt.sign({ phoneNumber: args.phoneNumber, requestId: result.request_id }, 'mysecret' );
          ctx.req.response.cookie('token', token, {
              httpOnly: true,
              maxAge: 1000*60*60*24*365
          })
        return phoneNumber
    },
`Fran Dios
10/29/2018, 3:58 AMupdateManyEntities in 1.20-beta.1? my generated prisma.graphql changed every updateManyX parameters from data: XUpdateInput to data: XUpdateManyInput and now my app fails (got invalid value {...}; Field "..." is not defined by type XUpdateManyInput.).
I can’t see related breaking changes in the release notes before 1.20-beta.1 so I assume the breaking change is in this version which is not yet published (but development servers are using it)hinsxd
10/29/2018, 9:18 AMclient to perform pagination with relay’s xxxsConnection model,  only simple first, skip, before, etc… are used instead.
I have tried to import Query.postsConnection from the generated schema and used prisma.postsConnection(args) in resolver, but I got the classic must have a sub selection error. Is it true that Prisma encourage us not to use relay connection to do pagination?Dylan DPC
10/29/2018, 9:19 AMnilan
10/29/2018, 9:52 AMCollins Ifunanya
10/29/2018, 9:57 AMYonben
10/29/2018, 10:14 AMKudakwashe Mupeni
10/29/2018, 10:29 AM