refactor: extract core GraphQL into pkg/beangraph (Refs: beans-rvfe)#170
Merged
refactor: extract core GraphQL into pkg/beangraph (Refs: beans-rvfe)#170
Conversation
- Create pkg/beangraph/ package with CoreResolver struct for core bean CRUD operations (queries, mutations, bean field resolvers, filters, ETag/validation helpers) - Move gqlgen model types from internal/graph/model/ to pkg/beangraph/model/ - internal/graph/Resolver now embeds *beangraph.CoreResolver and delegates core operations; UI-only resolvers stay in internal/graph/ - CLI commands (create, list, show, update, delete, roadmap) and TUI now use beangraph.CoreResolver directly, removing their dependency on internal/graph and its UI-specific imports (agents, worktrees, terminals) - Only graphql.go and serve.go still import internal/graph (they need the full gqlgen executable schema)
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
1 participant
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
pkg/beangraph/package withCoreResolverstruct containing all core bean operations (CRUD, relationships, filtering, ETag validation) — depends only onpkg/beancore, no UI importsinternal/graph/model/topkg/beangraph/model/so they're part of the public API surfaceinternal/graph/Resolvernow embeds*beangraph.CoreResolverand delegates core operations; UI-only resolvers (agents, worktrees, terminals, git diffs) stay ininternal/graph/beangraph.CoreResolverdirectly, removing their dependency oninternal/graphand its heavy UI importsThis prepares for a potential future split of Beans UI into a separate project — the core GraphQL API is now cleanly separated from the serve-specific GraphQL.
Test plan
go test ./...)schema.graphqlsdirectly)beans list,beans create,beans show,beans update,beans deletework as beforebeans servestarts and the UI works normallybeans query '{ beans { id title } }'returns results