[GF-BE-13] Build resource and equipment booking backend module

[yusuftomilola]

Problem

ManageHub only supports booking workspace slots (desks, offices, meeting rooms). There is no way to book individual equipment or resources such as projectors, podcast booths, standing desks, or camera rigs. Hubs that offer these items have no way to manage or monetise them through the platform.

Proposed Solution

Create a new NestJS module at backend/src/resources/ with two entities.

Entity: Resource

• id (UUID), name (string), description (text)
• type (enum: projector | monitor | whiteboard | podcast_booth | camera | standing_desk | locker | other)
• totalQuantity (integer), pricePerHour (integer, kobo — 0 for free resources)
• isAvailable (boolean, default true)
• images (JSONB array of URLs, nullable)
• locationId (UUID FK → locations, nullable)
• createdAt, updatedAt

Entity: ResourceBooking

• id (UUID), resourceId (FK → resources), userId (FK → users)
• startTime (timestamp), endTime (timestamp)
• quantityRequested (integer, default 1)
• status (enum: pending | confirmed | cancelled | completed)
• paymentId (UUID FK → payments, nullable)
• totalAmount (integer, kobo)
• createdAt, updatedAt

Endpoints:

Method	Path	Access
POST	/resources	Admin
GET	/resources	Public
GET	/resources/:id	Public
PATCH	/resources/:id	Admin
DELETE	/resources/:id	Admin
GET	/resources/:id/availability	Public — accepts date query param
POST	/resources/:id/book	Authenticated member
GET	/resources/bookings/my	Authenticated member

Acceptance Criteria

• Both entities created with TypeORM migrations
• Availability check validates requested quantity against totalQuantity - sum of confirmed bookings for the time slot
• POST /resources/:id/book initiates payment via PaymentsService for paid resources
• ResourcesModule is registered in AppModule

[feyishola]

Hi im Feyishola a software developer with over 4 years of experience. pls let me handle this

[grantfox-oss]

🦊 GrantFox — @feyishola has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1088)
2. Your PR will be reviewed by the DistinctCodes maintainers

Good luck! Track your progress on GrantFox.

[nanaf6203-bit]

@nanaf6203-bit has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

can I please take this issue please?

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

[drips-wave]

Congratulations, @nanaf6203-bit! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @nanaf6203-bit: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @nanaf6203-bit has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1088)
2. Your PR will be reviewed by the DistinctCodes maintainers

Good luck! Track your progress on GrantFox.