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

    sashko

    10/19/2016, 7:21 AM
    still some work to do :]
  • s

    sashko

    10/19/2016, 7:21 AM
    I was thinking it would be cool to do something like preact
  • s

    sashko

    10/19/2016, 7:21 AM
    where you can actually use the same syntax, but with no caching
  • s

    sashko

    10/19/2016, 7:21 AM
    so it's like 5kb or something
  • s

    sashko

    10/19/2016, 7:21 AM
    and then you can upgrade to the fancy cache edition when you want to
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:22 AM
    yah that would be amazing
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:22 AM
    one thing i'm experimenting with is pulling the data field requirements from the virtual node tree.
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:22 AM
    not sure if this is possible with react
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:22 AM
    but you can walk the virtual nodes before rendering
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:22 AM
    in preact
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:23 AM
    so, you could pull out additional information from the tree and make the query at that point
  • s

    sashko

    10/19/2016, 7:23 AM
    yeah.. I think that will make life harder down the road: https://medium.com/apollo-stack/5-benefits-of-static-graphql-queries-b7fa90b0b69a
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:23 AM
    not sure exactly how to combine the query at this point
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:23 AM
    oh interesting
  • s

    sashko

    10/19/2016, 7:23 AM
    it's one of the things that makes Relay really complicated, and in fact Relay 2 is getting rid of that entirely
  • s

    sashko

    10/19/2016, 7:23 AM
    basically, it's a huge advantage to not need to load any code to get your queries
  • s

    sashko

    10/19/2016, 7:24 AM
    but you can get a lot of what you're looking for with fragments
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:24 AM
    ah interesting, yah that's what i'm doing now
  • s

    sashko

    10/19/2016, 7:24 AM
    so you just statically add fragments to the query
  • s

    sashko

    10/19/2016, 7:24 AM
    yeah
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:24 AM
    just defining graphql queries in varaibles at the top and executing them
  • s

    sashko

    10/19/2016, 7:25 AM
    right, but fragments will let you keep the static aspect, while not having to write the whole query at the top
  • s

    sashko

    10/19/2016, 7:25 AM
    the only difference is, I don't think it's a good idea to actually walk the UI to get the fragments
  • s

    sashko

    10/19/2016, 7:25 AM
    IMO you just want static fragment references
  • s

    sashko

    10/19/2016, 7:26 AM
    here's a similar conversation: https://github.com/apollostack/graphql-tag/pull/12
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:26 AM
    interesting, okay i've got some good reading.
  • s

    sashko

    10/19/2016, 7:26 AM
    anyway, I gotta go, trying to finish some stuff up (apollo client 0.5!!)
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 7:27 AM
    sweet, appreciate all the info. thanks!
  • s

    sashko

    10/19/2016, 7:27 AM
    yeah np, thanks for a good chat
  • m

    Matt Mueller (Prisma Client PM)

    10/19/2016, 8:17 AM
    @sashko one more question: how does the
    ApolloProvider
    in apollo-react talk to the
    graphql
    components?
1...293031...637Latest