Description
Power Active / Drafted / Completed tabs on the Quests hub from API instead of hardcoded list data.
User Story
As a Founder,
I want my Quests page list to be real,
so that it matches on-chain/API state.
Requirements and Context
- Files:
Questlist.tsx, QuestItem.tsx, quests page
- Map mission status → tabs; link rows to
/creator/quests/[id]
- JWT required
Suggested Implementation
// Reuse same /missions/me client as dashboard
// Filter by status for tabs
Acceptance Criteria
Submission Guidelines
- Branch:
feat/fe-creator-quests-api
- Depends on:
[FE] Creator Quests hub UI, [FE] SEP-10 login on creator routes
- PR:
feat(frontend): wire creator quests list to API
Description
Power Active / Drafted / Completed tabs on the Quests hub from API instead of hardcoded list data.
User Story
As a Founder,
I want my Quests page list to be real,
so that it matches on-chain/API state.
Requirements and Context
Questlist.tsx,QuestItem.tsx, quests page/creator/quests/[id]Suggested Implementation
Acceptance Criteria
Submission Guidelines
feat/fe-creator-quests-api[FE] Creator Quests hub UI,[FE] SEP-10 login on creator routesfeat(frontend): wire creator quests list to API