Monday, 8 September - Wednesday, 10 September, 2025 In-Person Only | Amsterdam, Netherlands
The Sched app allows you to build your schedule but is not a substitute for your event registration. You must be registered for GraphQLConf 2025 to participate in the sessions.
Please note: This schedule is automatically displayed in Central European Summer Time (UTC+2). To see the schedule in your preferred timezone, please select from the drop-down located at the bottom of the menu to the right.
IMPORTANT NOTE: Timing of sessions and room locations are subject to change.
Sign up or log in to add sessions to your schedule and sync them to your phone or calendar.
The most natural way to understand fragments is as a reusable part of a query. We at Meta know that this isn't true and can lead to a world of pain when it comes to making sure the data you fetch matches the code that uses that data (no over-fetching).
The worst part is both the GraphQL spec and the educational materials mention re-use for fragments as part of their value: "Fragments allow for the reuse of common repeated selections of fields, reducing duplicated text in the document."
This talk will explain what we've learned is the best way to use fragments (as subcomponents you convert to in order to pass to the logic that is tied to that fragment).
We will use Relay's per-file graphql co-location as a demonstration of this philosophy in action
