Update useKindeAuth to new implementation with deprecation warning#439
Conversation
|
No actionable comments were generated in the recent review. 🎉 WalkthroughAdds an exported Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@src/frontend/factories/feature-flag-factory.ts`:
- Around line 5-10: The flagDataTypeMap constant is missing the "j" key required
by the KindeFlagTypeCode union; update flagDataTypeMap to include j: "json" so
it satisfies Record<KindeFlagTypeCode, KindeFlagTypeValue> (i.e., add the "j"
entry to the exported flagDataTypeMap object to match the
KindeFlagTypeCode/"b"|"i"|"s"|"j" and KindeFlagTypeValue types).
9e5cc7d to
17a9bbd
Compare
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Explain your changes
Update the
useKindeAuthfunction to point to the newuseKindeBrowserClientimplementation and add a deprecation warning. This change prepares for the eventual removal ofuseKindeAuthin a future major version.Breaking changes
None.
useKindeAuth()returns the sameKindeStatetype as before - it just works now.Checklist
🛟 If you need help, consider asking for advice over in the Kinde community.