Skip to content

Add server-side route handlers for dashboard data #49

Description

@Lakes41

Difficulty: Advanced

Type: Feature

Summary

Create server-side API routes for dashboard entities so the frontend can transition from direct mock imports to a stable backend boundary.

Current Behaviour

Dashboard pages can read data from local mock files. The README notes that all data is currently mock data, while the monorepo includes an integration client and webhook utilities.

Expected Behaviour

The dashboard should expose server-side route handlers for passes, guilds, members, activity, and settings, with mock-backed implementations first and live adapters later.

Suggested Implementation

Add route handlers under apps/dashboard/app/api/ that call typed services. Keep mock storage behind the service layer. Return consistent JSON response shapes and typed error responses.

Files or Areas Likely Affected

  • apps/dashboard/app/api/passes/
  • apps/dashboard/app/api/guilds/
  • apps/dashboard/app/api/members/
  • apps/dashboard/app/api/activity/
  • apps/dashboard/lib/data/
  • apps/dashboard/lib/api/

Acceptance Criteria

  • API routes exist for core dashboard entities
  • Routes call service modules instead of importing mock arrays directly
  • Routes return consistent success and error shapes
  • Routes validate query parameters
  • Pages can be migrated to the route-backed data layer
  • Tests cover at least one success and one failure path per route group

Additional Notes

Do not expose secrets in client responses. This issue should establish a server-safe boundary for later live integrations.

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial CampaignCampaign: Official Campaign

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions