Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[epic] imperatively loaded resolvers #62

Open
rbalicki2 opened this issue Apr 15, 2024 · 0 comments
Open

[epic] imperatively loaded resolvers #62

rbalicki2 opened this issue Apr 15, 2024 · 0 comments
Labels
details needed needs extra details before it is ready to be worked on

Comments

@rbalicki2
Copy link
Collaborator

  • useImperativeReference lets you imperatively load a new entrypoint (its naming sucks!)
  • We should be able to do that for a client field, e.g.
field Query.foo {
  bar @loadedImperatively #or  
  bar | loadedImperatively
}

Not really sure yet about the syntax.

  • This should be read out as an object with type { kind: 'NotLoaded', load: () => void } | { kind: 'Loading' } | { kind: 'Loaded', data, dispose: () => void }
  • Or something. I'm not really sure.

Open questions

  • How does this relate to refetching with different variables? Those should probably have similar read out types
  • Likewise, pagination should probably be similar
@rbalicki2 rbalicki2 added the details needed needs extra details before it is ready to be worked on label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
details needed needs extra details before it is ready to be worked on
Projects
None yet
Development

No branches or pull requests

1 participant