nsfmc’s avatarnsfmc’s Twitter Archive—№ 4,353

  1. …in reply to @ianstormtaylor
    ianstormtaylor i guess it sorta depends on where you draw the lines: lots of actions become graphql resolvers
    On twitter.com Twitter logo nsfmc’s avatar 2016 Oct 12 Mood 0
    1. …in reply to @nsfmc
      ianstormtaylor agree there's an aesthetic benefit to having all api interactions clustered in graphql, but if i squint, i feel like i've
      Permalink On twitter.com Twitter logo nsfmc’s avatar 2016 Oct 12 Mood +5 🙂
      1. …in reply to @nsfmc
        ianstormtaylor just shifted and organized some actions into one Relay.QL func & my relay containers kinda look like redux providers/etc
        Permalink On twitter.com Twitter logo nsfmc’s avatar 2016 Oct 12 Mood +2 🙂
        1. …in reply to @nsfmc
          ianstormtaylor my takeaway was that redux provided a way to communicate with a team about how and where to access data now on the client
          Permalink On twitter.com Twitter logo nsfmc’s avatar 2016 Oct 12 Mood 0
          1. …in reply to @nsfmc
            ianstormtaylor & that relay is a refinement + optimization of that pattern that clearly seps. queries/muts on client & resolvers on server
            Permalink On twitter.com Twitter logo nsfmc’s avatar 2016 Oct 12 Mood +1 🙂