-
-
Notifications
You must be signed in to change notification settings - Fork 3
Add back auth scaffolding #44
Comments
Not sure why you would need a table to do password resets 🤔 ? |
Sort of following in the foot steps of how Laravel does it. I suppose we don't really need one as we can still do it now. But I feel like it might be better to have a dedicated password resets to store the tokens. We could also better control the expirations of the token. Like password resets only valid for 24 hours or something. |
Its a good question. I don't like being TOO opinionated on something like that. We could take a similar approach of what we did with M3 and make different presets like
idk if I really want to maintaining all of these upgrades though between major releases ... idk. open for discussion lol. Have to balance what would be really cool as a framework and what we want to maintain, especially going forward into M4 |
Maybe as Tailwind CSS seems to be used more and more and it's not a frontend framework this could be the one we will maintain for the auth scaffolding ? For something more opiniated and complex, Laravel did Jetstream with different preset (Livewire and Inertia) but for CSS I guess they are using TailwindCSS. |
Need to relook at all the authentication scaffolding. Early days had a lot of rewrites in this.
We need to support controllers and routes for:
password_resets
)The text was updated successfully, but these errors were encountered: