Add handleRegistration() method to register page

[dododedodonl]

Description

When customizing the user creation process, the whole register method has to be overwritten. With this, only the creation itself can be customized.

When making this edit, I was not sure what return type to choose. I ended up with choosing Authenticatable, the one required for ->login(). Should the $user parameter of sendEmailVerificationNotification() not also be changed to Authenticatable instead of Model?

Visual changes

None

Functional changes

• Code style has been fixed by running the composer cs command.
• Changes have been tested to not break existing functionality.
• Documentation is up-to-date.

[zepfietje]

When making this edit, I was not sure what return type to choose. I ended up with choosing Authenticatable, the one required for ->login(). Should the $user parameter of sendEmailVerificationNotification() not also be changed to Authenticatable instead of Model?

Changing the param type of existing methods would be a breaking change, right?

Maybe @danharrin knows the reasoning for using Model instead of Authenticatable?

[danharrin]

Changing to Model for consistency. I don't think there's much reason to have one over the other, but there might be a situation where someone is implementing a custom login/registration flow that does not use Laravel's built in auth logic, so Authenticatable might not be applied. Model just feels safer considering we are interacting with Eloquent database features, and more open to extension.