Issue #3 — Workspace Management (Admin-Only)

[yusuftomilola]

Background

Admins need to register workspaces and manage their availability and pricing. This issue implements the three workspace-management write functions and the two workspace query functions.

Task

Building on Issue #2, add the following public functions:

1. pub fn register_workspace(env, caller, id, name, workspace_type, capacity, hourly_rate) -> Result<(), Error>

   • Call Self::require_admin(&env, &caller)?.
   • Return Error::InvalidCapacity if capacity == 0.
   • Return Error::InvalidRate if hourly_rate <= 0.
   • Return Error::WorkspaceAlreadyExists if DataKey::Workspace(id.clone()) exists in persistent storage.
   • Build a Workspace struct with is_available: true and created_at: env.ledger().timestamp().
   • Save to DataKey::Workspace(id.clone()) in persistent storage.
   • Append id to the WorkspaceList in instance storage.
   • Emit event: topic (symbol_short!("ws_reg"), id), data (name, workspace_type, capacity, hourly_rate).

2. pub fn set_workspace_availability(env, caller, workspace_id, is_available) -> Result<(), Error>

   • Require admin. Load workspace, return Error::WorkspaceNotFound if missing.
   • Toggle workspace.is_available, save back.
   • Emit event: topic (symbol_short!("ws_avail"), workspace_id), data (is_available,).

3. pub fn set_workspace_rate(env, caller, workspace_id, hourly_rate) -> Result<(), Error>

   • Require admin. Return Error::InvalidRate if hourly_rate <= 0.
   • Load workspace, return Error::WorkspaceNotFound if missing.
   • Update workspace.hourly_rate, save back.
   • Emit event: topic (symbol_short!("ws_rate"), workspace_id), data (hourly_rate,).

4. pub fn get_workspace(env: Env, workspace_id: String) -> Result<Workspace, Error>

   • Read DataKey::Workspace(workspace_id) from persistent storage, return Error::WorkspaceNotFound if absent.

5. pub fn get_all_workspaces(env: Env) -> Vec<String>

   • Read DataKey::WorkspaceList from instance storage, return an empty Vec if absent.

Files to modify

• contracts/workspace_booking/src/lib.rs

Acceptance criteria

• cargo check -p workspace_booking and cargo clippy -p workspace_booking -- -D warnings pass.
• Non-admin callers are rejected with Error(Contract, #2) (Unauthorized).
• Registering a duplicate workspace ID returns Error(Contract, #7) (WorkspaceAlreadyExists).
• capacity == 0 returns Error(Contract, #9) (InvalidCapacity).
• hourly_rate <= 0 returns Error(Contract, #10) (InvalidRate).
• get_workspace returns the correct struct after registration.
• get_all_workspaces returns IDs in registration order.
• Rate change via set_workspace_rate is reflected in the stored workspace.

Technical notes

• WorkspaceList lives in instance storage (contract-wide index); workspace records live in persistent storage.
• Rate changes apply only to future bookings — existing bookings already recorded amount_paid.

[soma-enyi]

Gm Gm Maintainer!!!!
I would like to work on this issue!!!!

[shamoo53]

hi, i have carefully gone through the instructions on how to implement the workspace management
kindly assign this issue
ETA 2hrs

[Emmanuelluxury]

I’d like to work on this issue because it sits at the intersection of system design, financial logic, and secure contract architecture — areas I actively specialize in and enjoy building within. The problem requires careful handling of state transitions, precision math, and security constraints, which makes it both technically meaningful and impactful to the overall reliability of the protocol.

[anonfedora]

I'm Anonfedora, I'm a Fullstack Blockchain Engr. I'm proficient in Rust (soroban), Rust serverside with Axum and tokio, Nestjs, epxressjs have vast experience in contributing and building on the Stellar ecosystem with the Rust using soroban's SDK.
I'm also good at comprehensively testing features.
ETA: < 8 hours

[gelluisaac]

I’m interested in tackling this! I have a strong background in smart contract development and full-stack systems, so I'm well-equipped to handle the requirements here. Could you please assign this to me?

[ryzen-xp]

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: 14 hours

[A6dulmalik]

Hi,
I’d like to work on the Workspace Management feature.

I’m comfortable with Rust and smart-contract development and would be happy to implement the required workspace management functions building on the existing structure from Issue #2. Specifically, I plan to:

• Implement the admin-only write functions:

  • register_workspace
  • set_workspace_availability
  • set_workspace_rate

• Implement the query functions:

  • get_workspace
  • get_all_workspaces

• Ensure proper validation (InvalidCapacity, InvalidRate, WorkspaceAlreadyExists, WorkspaceNotFound)

• Store workspace records in persistent storage and maintain the WorkspaceList index in instance storage

• Emit the specified events (ws_reg, ws_avail, ws_rate)

• Run cargo check and cargo clippy -D warnings to ensure the implementation passes all checks.

I’ll also make sure the acceptance criteria are fully satisfied, including admin authorization checks and correct ordering of workspace IDs in WorkspaceList.

If the issue is available, I’d be glad to take it on.
Thank you