25 lines
934 B
Markdown
25 lines
934 B
Markdown
Story Draft Checklist — 1.7 Contact Smart Form
|
|
|
|
1. Goal & Context Clarity
|
|
- PASS — Guided fields, success page, optional persistence defined.
|
|
|
|
2. Technical Implementation Guidance
|
|
- PARTIAL — API route contract and envs should be specified explicitly.
|
|
- Proposed envs: `NEXT_PUBLIC_WEB3FORMS_ACCESS_KEY` (existing), `CF_CONTACT_ENDPOINT`, `CF_CONTACT_AUTH` (optional).
|
|
|
|
3. Reference Effectiveness
|
|
- PASS — File paths and components referenced; migration path from Web3Forms clear.
|
|
|
|
4. Self-Containment Assessment
|
|
- PASS — Assumptions and constraints explicit (no Prisma changes; no PII logging).
|
|
|
|
5. Testing Guidance
|
|
- PASS — Validation scenarios, success redirect, and regression scope defined.
|
|
|
|
Final Assessment: NEEDS REVISION (minor)
|
|
- Clarity score: 8/10
|
|
- Issues:
|
|
- Lock down API response shape (e.g., `{ ok: boolean, message?: string }`).
|
|
- Document exact rate limit policy (e.g., 5/min/IP) to test against.
|
|
|