You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we have now a Fragment store where we can .get(), we could probably add another function: .refetch()
Is there the need to explicitly set @refetchable?
not every fragment is refetchable, it has to be defined on a type that either extends Node or has a custom type resolution defined. @refetchable would act as a mark to the artifact generator that it needs to generate the appropriate queries and verify the config.
edit: If the queries were computed at runtime, we might be able to do away with it 🤔
AlecAivazis
added
SvelteKit
Issues related to the SvelteKit integration
Router
Issues related to the React framework
Core
Issues related to the core infrastructure
and removed
SvelteKit
Issues related to the SvelteKit integration
Router
Issues related to the React framework
labels
Sep 10, 2023
There should be a
@refetchable
directive that labels fragments onNode
orQuery
as refetchable. The api could look something like this:The text was updated successfully, but these errors were encountered: