josephsavona

3 ms·

1. 1.▲
   by josephsavona 9y ago

   Hey! I'm Joe and work on the Relay core team. These are good questions: why does Relay Modern have garbage collection? Is that just a fancy name for cache eviction? Let's put aside naming for a moment. Relay stores GraphQL data in
2. 2.▲
   by josephsavona 9y ago

   Thanks for the feedback! > but there's no mention of subscriptions or client-side state control The blog post didn't cover all the new features, but both of these use-cases are supported in Relay Modern - https://fac
3. 3.▲
   by josephsavona 9y ago

   In general yes, garbage collection in Relay Modern is meant to help constrain growth of memory usage during the course of a session. This is where the declarative nature of GraphQL is helpful; unlike Redux which is accessed via arbitrary se
4. 4.▲
   by josephsavona 9y ago

   Hi! I'm Joe from the Relay team. Good questions! It isn't quite as straightforward as you might expect - the interconnected nature of graph-like data means that strategies that work for HTTP don't necessarily apply. For exa
5. 5.▲
   by josephsavona 9y ago

   Agree that this is overall accurate, especially wrt to Relay Classic. For Relay Modern, however: > 2. Relay doesn't have as many facilities for updating the store and working with mutation results. Apollo and Relay Modern are about
6. 6.▲
   by josephsavona 9y ago

   Hi, I'm Joe also on the Relay team. Relay Modern (as with previous versions) supports an injectable network layer. This allows each application to customize how to communicate with its GraphQL server using whatever transport protocol i