fix(auth): fixes userattributes type#2139
Conversation
The UserAttributes type used currentPassword (camel-case) but the Auth server expects current_password (snake-case)
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Cache: Disabled due to Reviews > Disable Cache setting Disabled knowledge base sources:
📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis change renames a single optional property in the UserAttributes interface from 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 |
@supabase/auth-js
@supabase/functions-js
@supabase/postgrest-js
@supabase/realtime-js
@supabase/storage-js
@supabase/supabase-js
commit: |
🔍 Description
The UserAttributes type used currentPassword (camel-case) but the Auth server expects current_password (snake-case)
What changed?
UserAttributetypeWhy was this change needed?
Bad typing would cause the Auth server to reject all password change attempts if current_password was required
📝 Additional notes
This feature isn't active yet on any Auth servers, but will be soon