-
@mjackson Caveat for my (upcoming) response: our projects haven't yet been updated to utilize the new hooks-based API, which looks like it is more dev-friendly. It looks like we'll be changing that for our mobile apps soon github.com/artsy/eigen/issues/6080 🕺
-
@mjackson Having said that -- there is a lot of ceremony & boilerplate when connecting components to relay, and it's not exactly intuitive what all of it is for without understanding relay implementation details. Note the "before" in @MounirDhahri's comment here - github.com/artsy/eigen/issues/6080#issuecomment-1020347576.
-
@mjackson @MounirDhahri Generally when engineers start contributing at Artsy, it's in the form of smaller feature development. So we come into this codebase and look for examples to copy, and depending on the complexity, there can be a lot of cargo-culting and tweaking until it works.
-
@mjackson @MounirDhahri Relay uses a different level/type of abstraction than anything I've ever worked with, and I think that makes it hard to fully understand how all the pieces fit together without spending some time reading & learning.
-
@mjackson @MounirDhahri We wrote/are writing (slowly) github.com/artsy/relay-workshop with the intention of making this easier for new devs to the team -- hoping to explain the concepts before throwing them into the fire.
-
@mjackson @MounirDhahri We're also hopefully migrating to hooks soon, and I think that could also help...but it also might just mean we need to update the learning exercises, because it's still a unique abstraction.
-
@mjackson @MounirDhahri From a coworker via slack (who isn't on twitter): Conventions!! Once you know the conventions its easy, but you have to satisfy the compiler, and to satisfy the compiler you have to know the conventions, and to learn the conventions is…tricky. It gets more flexible with hooks.