https://www.prisma.io/ logo
Join Slack
Powered by
# prisma-whats-new
  • m
    what data type should I use for a JSON field type when I call the mutation, e.g. mutation 
    createEvent($someObject: WHATGOESHERE?
  • s
    I believe it should be Json
  • n
    you can also read that up in GraphiQL
  • n
    in the GraphiQL docs
  • n
    hey @tonietto 👋
  • m
    hey guys - so I’m getting a scala error - I deleted a required field from my model and the query is still expecting it
  • m
    when I try to do a create mutation
  • m
    Error `Query does not pass validation. Violations: Cannot query field ‘oldDeletedField’ on type … line 5 column 5 ...
  • n
    can you go ahead and make some schema changes?
  • n
    for example, change the description of any model
  • m
    made an edit - but still giving me an error
  • m
    should I try renaming the field and then renaming it back?
  • n
    does that error occur when you run the mutation
  • n
    or did GraphiQL complain before execution?
  • m
    only after I run the mutation in the response do I get the error
  • m
    and looking in the db - the insert happens
  • m
    GraphIQL does not complain and autocompletes the correct updated fields
  • n
    hmm so the error is returned in the error part of the response?
  • n
    can you send a Screenshots?
  • m
    Copy code
    {
  "data": {
    "createEvent": null
  },
  "errors": [
    {
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "createEvent"
      ],
      "code": 4011,
      "message": "Something unexpected happened in an Action: 'Query does not pass validation. Violations:\n\nCannot query field 'title' on type 'Event'. (line 5, column 5):\n    title\n    ^' - 'sangria.execution.Executor.execute(Executor.scala:86),sangria.execution.Executor$.execute(Executor.scala:351),cool.graph.client.mutactions.SyncDataItemToAlgolia.performQueryWith(SyncDataItemToAlgolia.scala:120),cool.graph.client.mutactions.SyncDataItemToAlgolia.execute(SyncDataItemToAlgolia.scala:66),cool.graph.ClientMutation.cool$graph$ClientMutation$$runWithErrorHandler$1(ClientMutation.scala:107),cool.graph.ClientMutation$$anonfun$cool$graph$ClientMutation$$performGroup$1$1.apply(ClientMutation.scala:118),cool.graph.ClientMutation$$anonfun$cool$graph$ClientMutation$$performGroup$1$1.apply(ClientMutation.scala:116),scala.collection.immutable.List.map(List.scala:273),cool.graph.ClientMutation.cool$graph$ClientMutation$$performGroup$1(ClientMutation.scala:116),cool.graph.ClientMutation$$anonfun$2$$anonfun$apply$6.apply(ClientMutation.scala:134),cool.graph.ClientMutation$$anonfun$2$$anonfun$apply$6.apply(ClientMutation.scala:134),cool.graph.FutureUtils$.runFuturesInSerial(Utils.scala:157),cool.graph.FutureUtils$$anonfun$runFuturesInSerial$1.apply(Utils.scala:157),cool.graph.FutureUtils$$anonfun$runFuturesInSerial$1.apply(Utils.scala:157),scala.concurrent.Future$$anonfun$flatMap$1.apply(Future.scala:253),scala.concurrent.Future$$anonfun$flatMap$1.apply(Future.scala:251),scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32),scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121),scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260),scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.pollAndExecAll(ForkJoinPool.java:1253),scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1346),scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979),scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)'",
      "requestId": "ciygptxykcw8s01594v91tuug"
    }
  ]
}
  • n
    ahh
  • n
    seems to be another Algolia bug then
  • n
    or rather
  • n
    is the field still included in your Algolia index?
  • m
    ah yes it is - lemme remove it and see what haappens
  • n
    👍
  • m
    it’s good now
  • n
    cool!
  • n
    I'll add an issue anyway
  • m
    maybe a more descriptive error would be enough
1...909192...637Latest