https://www.prisma.io/ logo
Join SlackCommunities
Powered by
# prisma-whats-new
  • m
    @Raeesaa Have you been able to resolve issue https://github.com/graphcool/prisma/issues/1909#issuecomment-366157321 by using the beta release? Im still getting the issue after installing the beta release
    a
    n
    • 3
    • 6
  • a
    Is it possible to query relations through the generated Prisma db object? For example, when I set 
    const db = new Prisma({...})
    and then call 
    db.query.user({ where: id="id" })
    , the user object returned by Prisma does not include any of user’s relations.
    a
    • 2
    • 3
  • f
    anyone know of a way to force data deletion of a cluster endpoint in Prisma?
  • f
    @Fitch
    Copy code
    prisma local nuke
  • f
    yeah .. in the cloud .. not local .. im getting cached / hanging vers of data .. just switching cluster endpoints atm
  • r
    @Fitch this is also happenening to me but locally
  • r
    I just updated from 1.1 to 1.2
  • r
    and updated graphql-yoga
  • r
    which seems to be causing this issue
  • f
    im on 1.2.3 .. but Ill try the yoga updata .. gracias
  • r
    no wait
  • r
    I’m saying I didnt see this issue until I updated
  • f
    ah .. crap .. then maybe Im already past the update XD
  • f
    Ill nuke and adjust my package back
  • m
    hey, when I run 
    yarn
    , I get the warnings
    Copy code
    warning "prisma-binding > apollo-link@1.0.7" has incorrect peer dependency "graphql@^0.11.3 || ^0.12.3".
warning "graphql-yoga > apollo-server-express > apollo-server-core > apollo-cache-control@0.0.7" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0".
    Should I just ignore this or might this be a hint for local graphql version conflict/issues?
  • f
    yarn add graphql should sort it
  • m
    thx, that did the trick
    salute 1
  • r
    Is anybody else experiencing caching issues?
  • r
    when I make a mutation to add something, my subscription fired but the client doesn’t update
  • r
    if I do a brower refresh, the new data still doesn’t show up
  • r
    I wonder if because Graphql Yoga requires GraphQL 0.13
  • r
    but it looks like Apollo link, etc doesnt
  • r
    looks like there is a PR in Apollo Client for updating to 13
  • f
    Ive noticed this in the cli core both on prisma list and prisma import .. kind of odd .. trying to track it down
  • f
    Copy code
    cli-engine:plugins:manager requiring /usr/lib/node_modules/prisma/node_modules/prisma-cli-core +0ms
  portfinder:defaultHosts exports._defaultHosts is: [ '0.0.0.0', '127.0.0.1', '::1', '10.0.0.178', 'fe80::d:f6ff:fe1d:620c', '172.17.0.1', 'fe80::42:78ff:fe05:debb', '172.18.0.1', 'fe80::42:35ff:feb7:357f', 'fe80::849b:b6ff:fe07:7ec', 'fe80::bca3:c8ff:fea5:f0d1', 'fe80::2093:2bff:fef2:abf4', 'fe80::7027:a3ff:fecb:80dd' ] +0ms
  cli-engine:plugins:manager required +860ms
  plugin required command +866ms
  Environment [ 'graphcool-eu1', 'graphcool-us1', 'shared-public-demo' ] +0ms
  Environment { 'graphcool-eu1': '<https://graphcool-eu1.graphcool.cloud>',
  Environment   'graphcool-us1': '<https://graphcool-us1.graphcool.cloud>',
  Environment   'shared-public-demo': '<https://database-beta.graph.cool>' } +6ms
  StatusChecker setting status checker +1s
  • f
    If its trying to repeat actions in the core against a public endpoint instead of target .. could definitely cause the behaviour
  • r
    well the other thing is that prisma-binding has a dep of 0.13 for GraphQL, but when I try to 
    yarn add graphql
    on the client to install 0.13.1 everything breaks
  • a
    I fixed a similar issue to the ones mentioned above by adding
    Copy code
    "resolutions": {
  "graphql": "^0.13.0"
}
    to my package.json.
  • a
    Hey there, is there a commonly accepted terminology for GraphQL server-side queries that exist to collect data from another source? (e.g. Queries that live on the server and collect data from a REST API)
  • a
    Using the term query again seems a bit cluttered and confusing, as I tend to see that related to client-side queries to get data from the GraphQL server itself.
1...576577578...637Latest