Fix #180: null safety violation in ResetPasswordPage by adding backen…#197
Conversation
…adding backend availability checks
|
@Karelaking is attempting to deploy a commit to the Divya Tiwari's projects Team on Vercel. A member of the Team first needs to authorize it. |
✅ Deploy Preview for tiwaridivya25-devconnect ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Thanks for creating a PR for your Issue!
|
|
i have done my, please review it and let me know if their is any problem. |
There was a problem hiding this comment.
Pull request overview
Prevents crashes in ResetPasswordPage by guarding Supabase auth calls when running in demo mode or without backend configuration.
Changes:
- Import and use
isBackendAvailablealongsidesupabaseto gate backend operations. - Add early-return guards in
useEffect(session check) and password update submit handler. - Surface clearer user-facing messaging when password reset is unavailable.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 Description
Prevent crashes in
ResetPasswordPageby guarding Supabase auth calls when the backend is unavailable (demo mode or missing env).🎯 Type of Change
🔗 Related Issues
Closes #
📋 Changes Made
supabase.authcalls when backend is unavailable🧪 Testing
Testing Steps:
🎨 Screenshots/Demo
📦 Dependencies
✅ Checklist
Code Quality
npm run lintand fixed all issuesTesting & Functionality
Documentation
Git & Commits
Breaking Changes
📝 Additional Context
🔍 Reviewer Notes
🚀 Deployment Notes