Align frontend GraphQL schema with backend

[0xdevcollins]

The frontend's lib/graphql/schema.graphql is out of sync with the backend's auto-generated schema.gql. The frontend defines types (FEATURE, BUG, CLAIMED, Relay connections) that don't exist on the backend (FIXED_PRICE, MILESTONE_BASED, IN_PROGRESS, offset pagination).

Tasks

• Replace lib/graphql/schema.graphql with the backend's actual schema.gql (or symlink it)
• Update codegen.ts to point documents at a new lib/graphql/operations/ directory (see Issue 2)
• Run npm run codegen and verify generated.ts reflects the real backend types
• Update the Zod schemas in lib/api/bounties.ts to match the real BountyStatus and BountyType enums
• Update any UI components mapping over old enum values (open/claimed/closed → OPEN/IN_PROGRESS/COMPLETED/etc.)

Acceptance Criteria

• npm run codegen succeeds with zero warnings
• generated.ts types match the backend 1:1

[linear]

BOU-91

[coderabbitai]

🔗 Related PRs

#45 - Ekene001/bou 59 setup graphql client code generation [merged]
#47 - Add comprehensive GraphQL schema for bounties and projects API [merged]
#55 - feat-Implement Bounty Status Logic & Anti-Squatting [merged]
#73 - feat: Extend Form Components for Bounty Creation [merged]
#88 - feat: Implement bounties detail page [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

[devdeen213]

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

This is a schema drift cleanup, and I’m happy to sort it out — I’ll replace the stale lib/graphql/schema.graphql with the backend’s actual schema.gql (preferably symlinked to prevent this happening again), repoint codegen.ts to the new lib/graphql/operations/ directory, regenerate types to ensure generated.ts mirrors the backend exactly, then align the Zod schemas and UI enum mappings to the real BountyStatus and BountyType values so nothing references the old states; assuming no breaking API surprises, I can get everything synced and compiling cleanly within a day.

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

[Ekene001]

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

Hi, can i handle this task

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

[BigJohn-dev]

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

This issue appeals to me because it combines the challenge of solving complex frontend performance problems with the opportunity to deliver a smoother, more reliable user experience, while also sharpening my skills with emerging design and resolution patterns.

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

[SamixYasuke]

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

Hello, I'm an experienced developer, I'd like to work on this task, thanks

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

[Ekene001]

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

Hi, can I handle this task?

I've gone through the requirements and can have this ready in under 2 hours. I have experience managing GraphQL code generation and syncing frontend/backend types, so I’m familiar with the strict alignment required to keep the API layer from breaking.

I’ll tackle this by replacing the outdated schema.graphql with the actual backend schema and updating codegen.ts to point to the new operations directory. I'll then run the codegen to ensure generated.ts reflects the real backend types, like the new pagination and bounty status enums. Finally, I’ll update the Zod schemas in lib/api/bounties.ts and refactor any UI components that are still mapping to the old enum values so the entire flow is type-safe and in sync.

Please assign this to me.

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

[SudiptaPaul-31]

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

May I be assigned to this issue I have worked on several open-source projects and also an active open-source contributor and would love to contribute to this issue. I have worked with more than 30+ open-source projects and delivered quality pr's for them which led to faster project delivery

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