https://www.prisma.io/ logo
Join Slack
Powered by
# prisma-whats-new
  • a

    agartha

    06/09/2017, 8:14 PM
    Does deleting a file from the File Type not delete the actual file? Or do you have some kind of cleanup cron job running in the background?
    ❓ 1
    n
    • 2
    • 3
  • d

    dk0r

    06/09/2017, 8:35 PM
    In graph.cool's default
    user
    node, is there any conventional/best type (e.g. string, json, etc) for storing a user's names (first/middle/last/suffix) ?
  • d

    dk0r

    06/09/2017, 8:35 PM
    For example, you could use a string array by checking
    Store multiple values in this field

    http://i.imgur.com/LWd3Srv.png▾

  • d

    dk0r

    06/09/2017, 8:36 PM
    But I was kind of thinking of something more like:
  • d

    dk0r

    06/09/2017, 8:37 PM
    type
    User { id: ID! name: { first: string!, middle: string!, last: string!, suffix: string! } }
  • d

    dk0r

    06/09/2017, 8:38 PM
    Any suggestions as to which type would allow me to implement that ^
  • d

    dk0r

    06/09/2017, 8:43 PM
    Furthermore, how do I determine whether it is better to place individual fields on my
    User
    for name, address, phone, email, etc.. or if I should just place an info field on my user which contacts name,address,phone,email, etc..
  • d

    dk0r

    06/09/2017, 8:45 PM
    For example:
  • d

    dk0r

    06/09/2017, 8:45 PM
    User: { id: ID! name:[String!] address:[String!] phone:[Int!] email: String! }
  • d

    dk0r

    06/09/2017, 8:45 PM
    ..versus..
  • d

    dk0r

    06/09/2017, 8:46 PM
    User: { id: ID! info:{...} }
  • d

    dk0r

    06/09/2017, 8:46 PM
    where info contains name/address/phone/email
  • a

    agartha

    06/09/2017, 8:48 PM
    JSON would enable that
  • a

    agartha

    06/09/2017, 8:49 PM
    But you can't query directly on JSON fields (I think), so keep that in mind when deciding
  • d

    dk0r

    06/09/2017, 8:54 PM
    hmm --I want all the data to be queryable so it sounds like I'll need to have individual fields for each: first/middle/last/suffix/address/telephone/email/etc..
  • d

    dk0r

    06/09/2017, 8:55 PM
    @nilan Per the above discussion, are JSON fields non-queryable?
    n
    a
    • 3
    • 17
  • a

    agartha

    06/09/2017, 8:58 PM
    With queryable, I meant can be used for filtering, ordering, etc.
  • a

    agartha

    06/09/2017, 8:58 PM
    they will show up in query results of course
  • a

    agartha

    06/09/2017, 8:59 PM
    If you want to query a list of users ordered by last name, and last name is part of a JSON field, you can't do that
  • a

    agartha

    06/09/2017, 9:00 PM
    JSON fields are meant to be used to incoming data of which the structure is not known beforehand (user defined fields for example) or similar use cases
    🤔 1
  • a

    agartha

    06/09/2017, 9:02 PM
    Question: speaking of ordering, does anyone know what's the collation used for ordering?
    ❓ 2
    n
    • 2
    • 7
  • a

    agartha

    06/09/2017, 11:13 PM
    Hi guys, was playing around a bit with graphdoc to generate API documentation. I published the generated docs here in case anyone wants to know what it looks like: https://schema-kgfnulgaal.now.sh/ The link to graphdoc is on the API documentation pages. Cheers!
    👍 4
    🤔 1
  • s

    sunrising

    06/10/2017, 8:53 AM
    hi! i am integrating stripe payements following this tutorial: https://www.graph.cool/docs/tutorials/stripe-payments-with-mutation-callbacks-using-micro-and-now-soiyaquah7/
  • s

    sunrising

    06/10/2017, 8:54 AM
    it's all ok but i cannot understand what
    gc-pat
    is, at the step "Setup now", here: https://www.graph.cool/docs/tutorials/stripe-payments-with-mutation-callbacks-using-micro-and-now-soiyaquah7/#setup-now
  • s

    sunrising

    06/10/2017, 9:00 AM
    ok, found it! it is Permanent Authentication Token https://www.graph.cool/docs/reference/auth/authentication-tokens-eip7ahqu5o/#token-types
    n
    d
    m
    • 4
    • 37
  • w

    wallslide

    06/10/2017, 9:07 AM
    I'm having problems with debugging a permission query issue
    • 1
    • 6
  • w

    wallslide

    06/10/2017, 9:45 AM
    In a permission query, is the
    $node_id
    variable available for CREATE permissions? I thought it was, and according to the documentation it is, but on the right-hand side where all the available variables are listed, it doesn't show up.
    a
    • 2
    • 50
  • j

    juliancurrie

    06/10/2017, 11:13 AM
    Hi all..I've been working on this problem for the last two days in my React/GraphQL website using Auth0. I've followed the examples closely. I'm able to successfully create users in the Auth0 console, but the users never get created on the GraphQL Server. Any Help is greatly appreciated 🙂 I keep getting this error:
  • j

    juliancurrie

    06/10/2017, 11:13 AM
    Copy code
    proxyConsole.js:56 Error: GraphQL error: The provided idToken is invalid. Please see <https://auth0.com/docs/tokens/id_token> for how to obtain a valid idToken
        at new ApolloError (ApolloError.js:32)
        at QueryManager.js:109
        at <anonymous>
  • j

    juliancurrie

    06/10/2017, 11:16 AM
    I actually get the same error when using the hosted version of the tutorial here... http://apollo-auth0.netlify.com/
    a
    • 2
    • 77
1...224225226...637Latest