Phase 1: Authentication & Account Basics - 7 plans in 4 waves - Covers AUTH-01 through AUTH-05 requirements - Foundation for household features in Phase 2 - Ready for execution
193 lines
8.3 KiB
Markdown
193 lines
8.3 KiB
Markdown
---
|
|
phase: 01-authentication
|
|
plan: 06
|
|
type: execute
|
|
wave: 4
|
|
depends_on: ["01-03", "01-04"]
|
|
files_modified: ["lib/features/authentication/presentation/pages/login_page.dart", "lib/features/authentication/presentation/pages/signup_page.dart", "lib/features/authentication/presentation/pages/reset_password_page.dart", "lib/features/authentication/presentation/widgets/auth_form.dart"]
|
|
autonomous: true
|
|
user_setup: []
|
|
|
|
must_haves:
|
|
truths:
|
|
- "Login errors distinguish invalid password vs account not found"
|
|
- "Signup errors show specific failure reasons"
|
|
- "Password reset errors provide helpful guidance"
|
|
- "Loading states show during all auth operations"
|
|
- "Success messages provide clear confirmation"
|
|
artifacts:
|
|
- path: "lib/features/authentication/presentation/pages/login_page.dart"
|
|
provides: "Login with error handling"
|
|
min_lines: 50
|
|
- path: "lib/features/authentication/presentation/pages/signup_page.dart"
|
|
provides: "Signup with error handling"
|
|
min_lines: 50
|
|
- path: "lib/features/authentication/presentation/pages/reset_password_page.dart"
|
|
provides: "Password reset with error handling"
|
|
min_lines: 45
|
|
- path: "lib/features/authentication/presentation/widgets/auth_form.dart"
|
|
provides: "Enhanced form with error display"
|
|
min_lines: 40
|
|
key_links:
|
|
- from: "lib/features/authentication/presentation/pages/login_page.dart"
|
|
to: "lib/core/errors/auth_exceptions.dart"
|
|
via: "error type checking"
|
|
pattern: "InvalidCredentialsException|UserNotFoundException"
|
|
- from: "lib/features/authentication/presentation/widgets/auth_form.dart"
|
|
to: "lib/features/authentication/presentation/pages/login_page.dart"
|
|
via: "error state communication"
|
|
pattern: "error.*text|displayError"
|
|
---
|
|
|
|
<objective>
|
|
Integrate comprehensive error handling and user feedback in authentication flows.
|
|
|
|
Purpose: Provide clear, actionable error messages for all authentication scenarios to meet success criteria.
|
|
Output: Authentication system with proper error handling, loading states, and user-friendly feedback.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.opencode/get-shit-done/workflows/execute-plan.md
|
|
@~/.opencode/get-shit-done/templates/summary.md
|
|
</execution_context>
|
|
|
|
<context>
|
|
@.planning/PROJECT.md
|
|
@.planning/ROADMAP.md
|
|
@.planning/STATE.md
|
|
@.planning/phases/01-authentication/01-RESEARCH.md
|
|
</context>
|
|
|
|
<tasks>
|
|
|
|
<task type="auto">
|
|
<name>Enhance login page with error handling</name>
|
|
<files>lib/features/authentication/presentation/pages/login_page.dart</files>
|
|
<action>
|
|
Update LoginPage to:
|
|
1. Connect to AuthProvider for authentication
|
|
2. Handle loading states during login attempts
|
|
3. Display specific error messages based on exception type:
|
|
- "Invalid password" for InvalidCredentialsException
|
|
- "Account not found" for UserNotFoundException
|
|
- "Network error" for NetworkException
|
|
- "Session expired" for SessionExpiredException
|
|
- Generic error message for unknown errors
|
|
4. Show success message and navigate on successful login
|
|
5. Disable form inputs during submission
|
|
6. Include accessibility error announcements
|
|
7. Add proper error disposal when user starts typing again
|
|
8. Handle edge cases like empty form submission
|
|
9. Include proper error styling and positioning
|
|
</action>
|
|
<verify>Login page shows specific error messages for different failure scenarios and handles loading states properly</verify>
|
|
<done>Login page with comprehensive error handling and user feedback</done>
|
|
</task>
|
|
|
|
<task type="auto">
|
|
<name>Enhance signup page with error handling</name>
|
|
<files>lib/features/authentication/presentation/pages/signup_page.dart</files>
|
|
<action>
|
|
Update SignupPage to:
|
|
1. Connect to AuthProvider for registration
|
|
2. Handle loading states during signup attempts
|
|
3. Display specific error messages:
|
|
- "Email already in use" for EmailAlreadyInUseException
|
|
- "Password too weak" for WeakPasswordException
|
|
- "Invalid email format" for validation errors
|
|
- "Network error" for NetworkException
|
|
- Generic error message for unknown errors
|
|
4. Show password mismatch error before submission
|
|
5. Show success message on successful registration
|
|
6. Navigate to login after successful signup
|
|
7. Disable form inputs during submission
|
|
8. Include accessibility error announcements
|
|
9. Add proper error disposal when user starts typing again
|
|
10. Handle terms acceptance (placeholder)
|
|
</action>
|
|
<verify>Signup page provides specific feedback for all registration scenarios and validates password matching</verify>
|
|
<done>Signup page with comprehensive error handling and validation feedback</done>
|
|
</task>
|
|
|
|
<task type="auto">
|
|
<name>Enhance password reset pages with error handling</name>
|
|
<files>lib/features/authentication/presentation/pages/reset_password_page.dart</files>
|
|
<action>
|
|
Update ResetPasswordPage to:
|
|
1. Handle loading states during email sending
|
|
2. Display specific error messages:
|
|
- "Email not found" for UserNotFoundException
|
|
- "Too many requests" for rate limiting
|
|
- "Network error" for NetworkException
|
|
- Generic error message for unknown errors
|
|
3. Show success message with clear instructions
|
|
4. Display countdown before resend is allowed (if needed)
|
|
5. Include accessibility error announcements
|
|
6. Add proper error disposal when user changes email
|
|
7. Handle edge cases like empty email submission
|
|
8. Provide helpful error recovery instructions
|
|
9. Show proper loading indicators
|
|
</action>
|
|
<verify>Password reset page handles all error scenarios and provides clear user guidance</verify>
|
|
<done>Password reset page with comprehensive error handling and user guidance</done>
|
|
</task>
|
|
|
|
<task type="auto">
|
|
<name>Enhance auth components with error display</name>
|
|
<files>lib/features/authentication/presentation/widgets/auth_form.dart</files>
|
|
<action>
|
|
Update AuthForm to:
|
|
1. Accept optional error message prop
|
|
2. Display error messages below relevant fields
|
|
3. Style errors appropriately (red text, icons if needed)
|
|
4. Include accessibility announcements for errors
|
|
5. Auto-clear errors when user starts typing
|
|
6. Handle field-specific vs form-wide errors
|
|
7. Provide clear error positioning and styling
|
|
8. Include proper error boundaries
|
|
9. Support error recovery guidance
|
|
10. Maintain consistency across all auth forms
|
|
</action>
|
|
<verify>Auth form components display errors clearly and handle error state transitions properly</verify>
|
|
<done>Enhanced auth form components with integrated error display functionality</done>
|
|
</task>
|
|
|
|
<task type="auto">
|
|
<name>Add success feedback and loading indicators</name>
|
|
<files>lib/features/authentication/presentation/widgets/auth_button.dart</files>
|
|
<action>
|
|
Update AuthButton to:
|
|
1. Show loading spinner when in loading state
|
|
2. Disable button during loading
|
|
3. Change button text during loading (e.g., "Signing In...")
|
|
4. Add success state feedback (brief color change or checkmark)
|
|
5. Include haptic feedback on mobile (if available)
|
|
6. Add accessibility labels for loading state
|
|
7. Prevent double-tap during submission
|
|
8. Add proper visual transitions between states
|
|
9. Maintain consistent loading behavior across all auth buttons
|
|
10. Include error state styling if needed
|
|
</action>
|
|
<verify>Auth button provides clear loading feedback and prevents user confusion during submission</verify>
|
|
<done>Enhanced auth button with comprehensive state feedback</done>
|
|
</task>
|
|
|
|
</tasks>
|
|
|
|
<verification>
|
|
1. Login attempts show specific error messages for invalid password vs account not found
|
|
2. Registration attempts show specific error messages for email conflicts, weak passwords, etc.
|
|
3. Password reset requests handle all error scenarios with helpful guidance
|
|
4. Loading states appear consistently during all authentication operations
|
|
5. Error messages disappear when user takes corrective action
|
|
6. Success feedback is clear and appropriate
|
|
7. Accessibility features announce errors and state changes properly
|
|
</verification>
|
|
|
|
<success_criteria>
|
|
Authentication system with comprehensive error handling that meets all 5 success criteria for clear, actionable user feedback.
|
|
</success_criteria>
|
|
|
|
<output>
|
|
After completion, create `.planning/phases/01-authentication/01-06-SUMMARY.md`
|
|
</output> |