-
@samselikoff @ArtsyOpenSource It's definitely a steep learning curve. I don't know of any solid learning materials to improve that (which is why we started writing our own 😅). The docs have improved a lot with the most recent release (the one with hooks), but most of my learning came by breaking stuff.Permalink On twitter.com
Mood +6 🙂
-
@samselikoff @ArtsyOpenSource When I first started at Artsy I felt like I never would have been able to set Relay up on my own, I thought it was just too complicated...but the PR to set it up for our workshop was actually not awful: github.com/artsy/relay-workshop/pull/1Permalink On twitter.com
Mood +5 🙂
-
@samselikoff @ArtsyOpenSource Re: using it on a new project: I don't have much to compare it to, the only other significant react-to-graphql work I've done is with @RedwoodJS and I don't know exactly how much of @apollographql 's client is abstracted for me....Permalink On twitter.com
Mood +1 🙂
-
@samselikoff @ArtsyOpenSource @RedwoodJS @apollographql Having said that, I *love* the way components feel isolated with relay, with data concerns expressed right next to everything else, and the fact that relay bundles all queries for an entire tree into one request. I miss this with redwood.Permalink On twitter.com
Mood 0
-
@samselikoff @ArtsyOpenSource @RedwoodJS @apollographql And I think my conclusion is that yes, I *would* use it on a new project, given I'm further along the learning curve & I've worked through the setup in that above PR. I don't think I felt that way when it was newer to me. Sorry for the novel 😅On twitter.com
Mood +2 🙂
-
@samselikoff @ArtsyOpenSource @RedwoodJS @apollographql Oops, one last point -- I don't think I would use Relay if I wasn't also using TypeScript. It seems like it'd be really hard to work with the bits that Relay generates without TypeScript ensuring I wasn't mistyping names and such.Permalink On twitter.com
Mood 0