Difficulty: Advanced | Type: Feature
Background: NEXT_PUBLIC_FEATURE_EVENTS defaults to true in mock mode but false in prod, gating /events/*, implying the events module exists but isn't yet considered production-ready.
Problem: Without a documented reason the events module is prod-disabled, contributors have no clear target for what "done" looks like — the gap between "works in the demo" and "safe to ship" needs to be made explicit and closed.
Expected Outcome: A documented gap analysis between the current /events/* implementation and production requirements (error handling, empty/loading states, real data validation, access-gating correctness), followed by fixes closing that gap, with the flag flipped to true by default in prod once complete.
Suggested Implementation: Audit /events/* pages against the same production bar as the member/admin dashboards (loading states, error boundaries, gated-access correctness per resource policy), fix identified gaps, and update the default in lib/features.ts and .env.example once the module passes review.
Acceptance Criteria:
- A short audit doc/PR description lists every gap found and how each was addressed.
- Events pages have equivalent loading/error/empty-state handling to the rest of the app.
- Default flag value is flipped to
true for prod only after the above is complete and reviewed.
Likely Affected Files/Directories: app/events/*, lib/features.ts, .env.example
Labels: feature, GrantFox OSS, Maybe Rewarded, Official Campaign | FWC26
Difficulty: Advanced | Type: Feature
Background:
NEXT_PUBLIC_FEATURE_EVENTSdefaults totruein mock mode butfalsein prod, gating/events/*, implying the events module exists but isn't yet considered production-ready.Problem: Without a documented reason the events module is prod-disabled, contributors have no clear target for what "done" looks like — the gap between "works in the demo" and "safe to ship" needs to be made explicit and closed.
Expected Outcome: A documented gap analysis between the current
/events/*implementation and production requirements (error handling, empty/loading states, real data validation, access-gating correctness), followed by fixes closing that gap, with the flag flipped totrueby default in prod once complete.Suggested Implementation: Audit
/events/*pages against the same production bar as the member/admin dashboards (loading states, error boundaries, gated-access correctness per resource policy), fix identified gaps, and update the default inlib/features.tsand.env.exampleonce the module passes review.Acceptance Criteria:
truefor prod only after the above is complete and reviewed.Likely Affected Files/Directories:
app/events/*,lib/features.ts,.env.exampleLabels:
feature,GrantFox OSS,Maybe Rewarded,Official Campaign | FWC26