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

    tmoney

    12/05/2016, 8:08 AM
    ya I tried their other example from apollo docs:
    dataIdFromObject: o => o.id
  • t

    tmoney

    12/05/2016, 8:08 AM
    same error 😕
  • t

    tmoney

    12/05/2016, 8:09 AM
  • t

    tmoney

    12/05/2016, 8:14 AM
    I have a feeling it’s the way I have my networkInterface configured
  • e

    emilrmoeller

    12/05/2016, 8:34 AM
    Sorry i can’t help more, I’m developing with angular, so i actually don’t have dataFromObject 😕
  • t

    tmoney

    12/05/2016, 8:44 AM
    no problem, I’m getting closer. Looks like my updateQueries was malformed, have at least a different error now 😄
  • e

    emilrmoeller

    12/05/2016, 8:54 AM
    It’s quite complicated to be hournest
  • n

    nilan

    12/05/2016, 9:06 AM
    can you leave out the optimistic response for now?
  • e

    emilrmoeller

    12/05/2016, 9:07 AM
    i think @nilan ‘s advice is good in general, I’ve learned to add it as sugar coating because it really restricts the data as well after it gets entangled into it.
  • t

    tmoney

    12/05/2016, 9:14 AM
    for sure, but for a lot of the stuff I’m doing it will be pretty beneficial to have that feedback. I almost have it figured out. I’m getting it to add the optimistic update, and I see the UI update, but then it runs it again for some reason then errors and removes it haha
  • n

    nilan

    12/05/2016, 9:15 AM
    alright simple smile
  • e

    emilrmoeller

    12/05/2016, 9:19 AM
    Haha @tmoney that has been my biggest hurdle!!!!
  • e

    emilrmoeller

    12/05/2016, 9:21 AM
    It’s soo hard to debug. try console log the optimist response and the mutation result, make sure they are 100% identical
  • e

    emilrmoeller

    12/05/2016, 9:23 AM
    I get this error when the returned response is actually not the same as the optimistic one. It can be a field like
    published: true
    which in the returned one is
    published: false
    and then it behaves like this
  • t

    tmoney

    12/05/2016, 9:23 AM
    oh geez I think it’s calling it again one it gets back the results of the POST
  • t

    tmoney

    12/05/2016, 9:23 AM
    using the results from the POST
  • t

    tmoney

    12/05/2016, 9:23 AM
    ya so they need to be the same like you’re saying
  • e

    emilrmoeller

    12/05/2016, 9:24 AM
    Yeah it looks like 2 calls! I thought the same for hours until i realised that the first one is the optimstic and the second is the actual response
  • t

    tmoney

    12/05/2016, 9:25 AM
    guys thanks so much… I’ve finally done it… hahaha
  • t

    tmoney

    12/05/2016, 9:26 AM
    at least I actually understand it a lot better now 😉
  • e

    emilrmoeller

    12/05/2016, 9:26 AM
    Sweet @tmoney that was a killer for me to understand haha
  • e

    emilrmoeller

    12/05/2016, 9:27 AM
    I’m glad i could help
  • t

    tmoney

    12/05/2016, 9:27 AM
    @emilrmoeller huge help thank you
  • e

    emilrmoeller

    12/05/2016, 9:28 AM
    @tmoney is your name connected to the korean tmoney-card?
  • e

    emilrmoeller

    12/05/2016, 9:29 AM
    just realized i’ve seen that name before hehe
  • t

    tmoney

    12/05/2016, 9:29 AM
    haha no just first name starts with T, and has been my gamertag for a while now
  • e

    emilrmoeller

    12/05/2016, 9:30 AM
    haha alright! then a bonus info: T-money card is a travel card in south korea for taking public transport hehe
  • t

    tmoney

    12/05/2016, 9:31 AM
    haha ya I think I’ve used the logo as an avatar before cause that was what popped up when I googled images for tmoney haha
  • e

    emilrmoeller

    12/05/2016, 9:32 AM
    hahaha nice
  • n

    nilan

    12/05/2016, 9:47 AM
    great to hear @tmoney! I had some issues with updateQueries/optimisticResponse as well. nice that you worked it out
1...575859...637Latest