Skip to content

[Sprint] Statuses: Refactor handlers to use ObjectId and return Result<T> #85

@mpaulosky

Description

@mpaulosky

Problem

Status handlers have the same ObjectId/Result problems as other domains.

Depends On

Depends on: Foundation issue (standardize ObjectId in Shared commands/queries)

Files to Modify

  • src/Api/Handlers/Statuses/GetStatusHandler.cs — return Task<Result>
  • src/Api/Handlers/Statuses/ListStatusesHandler.cs — return Task<Result<IReadOnlyList>>
  • src/Api/Handlers/Statuses/CreateStatusHandler.cs — return Task<Result>
  • src/Api/Handlers/Statuses/UpdateStatusHandler.cs — return Task<Result>
  • src/Api/Handlers/Statuses/DeleteStatusHandler.cs — return Task<Result>
  • src/Api/Handlers/Statuses/StatusEndpoints.cs — map Result → HTTP responses

Acceptance Criteria

  • All 5 Status handlers return Task<Result>
  • No ObjectId.TryParse() in handler bodies
  • StatusEndpoints maps Result → proper HTTP status codes
  • Solution builds with zero errors and zero warnings

Metadata

Metadata

Assignees

No one assigned

    Labels

    go:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a membersquad:legolasAssigned to Legolas (Frontend Dev)squad:samAssigned to Sam (Backend Dev)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions