Write GraphQL operation documents (queries & mutations)

[0xdevcollins]

Depends on: #98
Today, no .graphql operation documents exist. The codegen found no documents to process, so generated.ts only contains types, not hooks. We need to write the actual query and mutation documents so the codegen can produce usable React Query hooks.

Tasks

Create lib/graphql/operations/ with the following files:

• bounty-queries.graphql

  query Bounties($query: BountyQueryInput) { bounties(query: $query) { ... } }
  query Bounty($id: ID!) { bounty(id: $id) { ... } }
  query ActiveBounties { activeBounties { ... } }
  query OrganizationBounties($organizationId: ID!) { organizationBounties(organizationId: $organizationId) { ... } }
  query ProjectBounties($projectId: ID!) { projectBounties(projectId: $projectId) { ... } }

• bounty-mutations.graphql

  mutation CreateBounty($input: CreateBountyInput!) { createBounty(input: $input) { ... } }
  mutation UpdateBounty($input: UpdateBountyInput!) { updateBounty(input: $input) { ... } }
  mutation DeleteBounty($id: ID!) { deleteBounty(id: $id) }

• submission-mutations.graphql

  mutation SubmitToBounty($input: CreateSubmissionInput!) { submitToBounty(input: $input) { ... } }
  mutation ReviewSubmission($input: ReviewSubmissionInput!) { reviewSubmission(input: $input) { ... } }
  mutation MarkSubmissionPaid($submissionId: ID!, $transactionHash: String!) { markSubmissionPaid(submissionId: $submissionId, transactionHash: $transactionHash) { ... } }

• Define shared fragments for BountyFields, SubmissionFields to avoid field duplication
• Run npm run codegen → verify hooks like useBountiesQuery, useCreateBountyMutation are generated

Acceptance Criteria

• generated.ts exports typed React Query hooks for every query and mutation
• Each generated hook uses the custom fetcher from lib/graphql/client.ts

[linear]

BOU-92

[coderabbitai]

🔗 Related PRs

#30 - feat: Implement React Query hooks for managing bounties [merged]
#32 - feat: introduce TanStack Query integration for bounties, including query options, keys, and prefetching utilities. [merged]
#34 - feat: Implement API-driven bounty fetching and display with dedicated loading, empty, and error UI components. [merged]
#45 - Ekene001/bou 59 setup graphql client code generation [merged]
#47 - Add comprehensive GraphQL schema for bounties and projects API [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[7maylord]

@7maylord has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, i am an experienced backend engineer and i can handle this issue, let me work on it, thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @7maylord to this issue.

[clintjeff2]

@clintjeff2 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Application to Work on Issue #99 – Write GraphQL Operation Documents (Queries & Mutations)

Hello,

I’m a frontend engineer with 6 years of experience working with GraphQL-heavy applications, especially around operation design, fragments, and codegen pipelines. I’ve handled setups where missing or poorly structured documents blocked hook generation, and I’m comfortable fixing this end-to-end in a clean, future-proof way.

This task is a natural follow-up to schema alignment work, and I’m confident working with GraphQL documents, fragments, React Query hooks, and custom fetchers.

For this issue, I would:

• Create lib/graphql/operations/ and add all required query and mutation documents
• Define shared fragments (BountyFields, SubmissionFields) to avoid duplication
• Ensure queries and mutations align exactly with the backend schema
• Run npm run codegen and verify all typed React Query hooks are generated
• Confirm each hook uses the custom fetcher from lib/graphql/client.ts
• Keep documents readable, consistent, and easy to extend

Estimated time: 6 hours

Telegram: @JeffersonYouashi

I’m ready to proceed as soon as Issue #98 is merged and can deliver a clean, review-friendly PR that unblocks frontend development.

Thank you for your consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @clintjeff2 to this issue.

[Ekene001]

@Ekene001 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I'd love to handle this task.

I've gone through the requirements and can have this ready in under 24 hours. I have experience setting up GraphQL operation layers and fragments for large-scale dApps, so I’m familiar with how to structure these documents to get the most out of automatic code generation.

I’ll tackle this by setting up the lib/graphql/operations/ directory and writing the specific queries and mutations required for bounties and submissions. I'll define shared fragments for BountyFields and SubmissionFields to keep the schema clean and maintainable. Finally, I’ll run the codegen and verify that all the typed React Query hooks are generated correctly and integrated with your custom fetcher, ensuring every operation is fully type-safe.

Looking forward to contributing.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ekene001 to this issue.

[Oluwatos94]

@Oluwatos94 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi @0xdevcollins, May I take up this task pls? I would get it done ASAP.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwatos94 to this issue.

[Hahfyeex]

@Hahfyeex has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Please assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hahfyeex to this issue.

[ALIPHATICHYD]

@ALIPHATICHYD has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi there maintainer, I’m ready to proceed on this issue to deliver a clean pr since I have experience in it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ALIPHATICHYD to this issue.