Define GraphQL Schema & Types

[0xdevcollins]

Define GraphQL schema matching existing REST API structure.

Tasks:

• Create schema.graphql with Bounty, Project, User types
• Define queries matching REST endpoints from lib/api/bounties.ts
• Define mutations for create/update/delete operations
• Add pagination types (replacing lib/api/types.ts:4-13)
• Setup subscriptions for real-time updates (replacing WebSocket events from lib/socket/client.ts)

# schema.graphql
type Bounty {
  id: ID!
  type: BountyType!
  projectId: String!
  projectName: String!
  projectLogoUrl: String
  issueTitle: String!
  issueNumber: Int!
  githubRepo: String!
  githubIssueUrl: String!
  description: String!
  rewardAmount: Float
  rewardCurrency: String!
  difficulty: DifficultyLevel
  tags: [String!]!
  status: BountyStatus!
  createdAt: String!
  updatedAt: String!
}

type BountyConnection {
  edges: [BountyEdge!]!
  pageInfo: PageInfo!
  totalCount: Int!
}

type Query {
  bounties(
    page: Int
    limit: Int
    status: BountyStatus
    difficulty: DifficultyLevel
    search: String
  ): BountyConnection!
  
  bounty(id: ID!): Bounty
}

type Mutation {
  createBounty(input: CreateBountyInput!): Bounty!
  updateBounty(id: ID!, input: UpdateBountyInput!): Bounty!
  deleteBounty(id: ID!): Boolean!
  claimBounty(id: ID!): Bounty!
}

type Subscription {
  bountyCreated: Bounty!
  bountyUpdated: Bounty!
  bountyDeleted: ID!
}

[linear]

BOU-60

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 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

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

✅ Successfully generated implementation plan.

💡 Use @coderabbitai <feedback> to replan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#19 - Implement Projects Discovery View (Projects tab) + build fixes (Tailwind v4 + UI typings) [merged]
#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]

---

🧪 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!

[EA10-lite]

@EA10-lite has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I'd love to work on this issue, my name is Emmanuel. I am a full-stack developer with 4 years of experience building Web and mobile applications.

I can confidently handle this issue.

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

[SudiptaPaul-31]

@SudiptaPaul-31 has applied to work on this issue as part of the Stellar Wave Program's 1st 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.

[ryzen-xp]

@ryzen-xp has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.

I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!

ETA: 24 hours

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

[ryzen-xp]

@ryzen-xp has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.

I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!

ETA: 24 hours

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

[aguilar1x]

@aguilar1x has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hey, I’m Matias Aguilar full-stack & smart contract dev in the Stellar ecosystem and Parhfinder role in stellar community.

I’ve been building RWA tooling and DeFi apps with Soroban, and I love tackling technical challenges with fast-moving teams. Super excited to jump in and help with this one!

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

[Chucks1093]

@Chucks1093 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello 0xdevcollins, I am a full stack engineer and I have built GraphQL layers on top of existing REST APIs before, and this is how I would approach it.

• Read through lib/api/bounties.ts and mirror each REST shape into GraphQL queries and inputs, keeping field names consistent so the frontend migration is mostly a mechanical swap.
• Create schema.graphql with Bounty, Project, and User types, then define Query and Mutation operations that match the existing create, update, delete, and claim flows, including proper enums for BountyType, DifficultyLevel, and BountyStatus.
• Replace pagination types from lib/api/types.ts by implementing Connection style pagination with edges, node, and pageInfo, and make sure it covers page, limit, and totalCount so REST features do not get lost.
• Map subscriptions to the existing socket events in lib/socket/client.ts by defining bountyCreated, bountyUpdated, and bountyDeleted, keeping payloads minimal and predictable so the client can update cache cleanly.
• Validate the schema by running it against sample REST responses, then add a small set of schema focused tests to ensure inputs, enums, and pagination types match what the REST layer actually returns.

This should be completed within about 6 to 10 hours.

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

[codewithzubair07]

@codewithzubair07 has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello Maintainers 👋,

I’d like to take ownership of Issue #44: Define GraphQL Schema & Types.

I have experience designing GraphQL schemas that mirror existing REST APIs, with a focus on clean type modeling, pagination best practices, and real-time updates via subscriptions. I understand the importance of keeping the schema aligned with current backend behavior to ensure a smooth transition for clients.

My approach

I will:

Create a schema.graphql file defining core domain types:

Bounty, Project, and User

Define queries that map directly to existing REST endpoints in lib/api/bounties.ts

Define mutations for create, update, delete, and claim operations with clear input types

Replace pagination logic from lib/api/types.ts with GraphQL-native pagination:

Connection, Edge, and PageInfo types

Set up subscriptions to replace current WebSocket events from lib/socket/client.ts, including:

bountyCreated

bountyUpdated

bountyDeleted

The schema will be:

Strongly typed

Consistent with the current REST response shape

Easy to extend as new fields or filters are added

Scope & guarantees

No backend logic refactors beyond schema definition

Schema strictly reflects existing API behavior

Clear naming and documentation to support frontend consumers

ETA

⏱ Estimated completion time: 6–8 hours

I’ll keep the PR well-scoped, easy to review, and aligned with existing project conventions. Happy to iterate quickly based on feedback.

Thanks for the opportunity!

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

[FabianSanchezD]

@FabianSanchezD has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hey Boundless team, I'm Fabian, full stack web3 dev! I'd like to take this issue, I have experience with GraphQL and I'd like to contribute to the project!

My ETA is less than 2 days. Thanks!

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

[KingFRANKHOOD]

@KingFRANKHOOD has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hello, I’m a smart contract developer with hands-on experience building with Rust and Soroban for smart contract development. GraphQl is also not new to me, hence, I believe I'll be a best fit for this issue

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an 24 HOURS while providing consistent updates throughout the process.

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