feat(data): add React data hooks and provider with swappable resolver#22
Merged
feat(data): add React data hooks and provider with swappable resolver#22
Conversation
Adds the runtime data layer for plugins: - DataResolver interface as the abstraction for data access - HttpResolver that speaks the GraphQL-like protocol over fetch - DataProvider React context that supplies the resolver to hooks - useQuery hook with loading/error/refetch (React Query-style) - useMutation hook with create/update/remove + auto-invalidation Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DataResolverinterface — the abstraction seam for swapping between local dev and production Workday APIsHttpResolverimplementation that speaks the GraphQL-like protocol (find,findOne,create,update,delete) overfetch()DataProviderReact context that supplies the resolver to child hooksuseQuery<T>(model, options?)hook — returns{ data, loading, error, refetch }(React Query-style)useMutation<T>(model)hook — returns{ create, update, remove, loading, error }with auto-invalidation of active queries after mutations@workday/everywhereThis is Phase 2 of the data bindings feature, building on the schema types and code generation from #21. Phase 3 (local data service as Vite middleware) will make the hooks functional during
everywhere view.Test plan
just checkpasses (typecheck + lint)🤖 Generated with Claude Code