fix(desktop): replace useActiveOrganization with collections data#881
Conversation
- Remove unused `name` field from invitations schema - Use collections to fetch organization data in MembersSettings - Use email directly for new user name in accept-invitation
📝 WalkthroughWalkthroughThe invitation system is refactored by removing the name field from the database schema, API responses, and user creation logic. The new user username now defaults to the email address. The MembersSettings component is updated to fetch organization data via local queries instead of using the activeOrganization hook. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
Summary
namefield from invitations schema (was causing Better Auth query failures)useActiveOrganization()with collections data in MembersSettingsTest plan
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.