Looks like cpojer.net has shipped his Relay-like client library. It gets most of the Relay benefits without the need for GraphQL as an intermediary type-system. Same features like data-masking, view composition and deep React integrations.
Worth an explore
fate.technology/posts/introd...
A neighbor said she saw agents dragging residents, including children, out of the building without any clothes on and into U-Haul vans. Kids were separated from their mothers, she said.
“It was heartbreaking,” she said.
@Suntimes @WBEZ
www.wbez.org/immigration/...
Ah no this is fragment arguments (exactly as you have them!) and then more on top later. Sorry didn’t realize we’d miss you at the conf!
Basically with scope you can add generic fragment spreads. But fragment arguments are needed more badly and sooner!
Also if you’ve ever wanted to thread a fragment through a callback, well. Maybe we need to get ahead of the spec again!
Yeah I’m fairly convicted that global scope for variables is worse than purely fragment local scope, but was what was needed for GraphQL in the moment of 2015.
I’d like to start pushing validation rules *requiring* fragment scoped definitions for all variables. But obviously can’t be spec.
@jovidecroock.com want to get mad at me at #GraphQLConf for putting up a new (related!) idea instead of helping push fragment arguments forward more?
And no it’s not fragment aliases either.
If you’re interested in how Meta gets ahead of the spec, I’ll be walking through how we decided we needed Defer/Stream. Now we’re finding new patterns that look kind of like Defer, but worse!
Let’s talk about how to bend GraphQL to a new domain with Async! graphql.org/conf/2025/sc...
Excited for #GraphQLConf Monday! See y’all in Amsterdam!
Interesting episode from Meta about GraphQL and their mobile apps
play.pocketcasts.com/podcasts/c4e...
SDL and Executables belong together. One mega document. Embrace everything