Skip to content

fix(data): correct GraphQL mutation input type name format#84

Merged
jheddings merged 1 commit into
mainfrom
fix/graphql-resolver-input-type-names
May 18, 2026
Merged

fix(data): correct GraphQL mutation input type name format#84
jheddings merged 1 commit into
mainfrom
fix/graphql-resolver-input-type-names

Conversation

@mackenziemcclaskey
Copy link
Copy Markdown
Collaborator

Summary

  • GraphQLResolver.create() was generating input type names with Summary_Create_Input, but the backend schema expects Summary_CreateInput
  • Same issue in GraphQLResolver.update(): Summary_Update_InputSummary_UpdateInput
  • Added tests for both create and update covering the correct input type name format

Test plan

  • Run npx vitest run tests/data/GraphQLResolver.test.ts — all 14 tests pass
  • Deploy a plugin that performs a create or update mutation and confirm it no longer fails with Variable '$input' cannot be non input type '..._Create_Input!'

🤖 Generated with Claude Code

Input types for create/update mutations were generated with
Summary_Create_Input / Summary_Update_Input, but the backend
schema expects Summary_CreateInput / Summary_UpdateInput.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@jheddings jheddings merged commit c7e37c3 into main May 18, 2026
2 checks passed
@jheddings jheddings deleted the fix/graphql-resolver-input-type-names branch May 18, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants