hooks: { before: createAuthMiddleware(async (ctx) => { if (ctx.path === "/error") { if (ctx.query && "error" in ctx.query && ctx.query.error === "banned") { throw ctx.redirect(`/banned`); } } }), },
hooks: { before: createAuthMiddleware(async (ctx) => { if (ctx.path === "/error") { if (ctx.query && "error" in ctx.query && ctx.query.error === "banned") { throw ctx.redirect(`/banned`); } } }), },
I'm on the latest version of better-auth (v1.2.10) I found those issues to be related #1580#1282
Those issues already exist I didn't want to open a new issue, but I need help with how to handle things correctly with the current version of better-auth. I’d appreciate guidance on the proper way to handle this in v1.2.10, especially with user context preserved.
Limitations: 1. banned page doesn't have any context about banned user - if I want to show the banReason I can't. - if I want to show a countdown timer I can't
Request: I'd appreciate taking another look at those issues mentioned above
Is this suited for github? #1581 To Reproduce most probably this is due to callback api route and in my case code is not generated as i cancel the process to choose another account logger do print ...
Is this suited for github? Yes, this is suited for github Is your feature request related to a problem? Please describe. I want to customize the response when a banned user tries to login. currentl...