-
-
Notifications
You must be signed in to change notification settings - Fork 892
feat(customPaths): Provides an option to modify api paths #2193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Review this PR on mrge.io |
@CrutchTheClutch is attempting to deploy a commit to the better-auth Team on Vercel. A member of the Team first needs to authorize it. |
commit: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AI code reviewer found 1 issue
this looks good to me! can we metion the option in the docs? it can be under reference/options |
@Bekacru Let me know if you would like any other changes to get this merged 🫡 |
I had a previous message stating this did not work for me on client side calls. This was incorrect, I was in a bad state locally. These changes appear to work on both the api as well as the better-auth client |
Anything I can do to help get this merged? @Bekacru |
A much needed option to allow consuming applications to have complete control over the endpoint paths. This is very useful in cases where specific api structures need to be followed while still being able to leverage better-auth.