Add email confirmation

[pxpm]

WHY

BEFORE - What was wrong? What was happening before this PR?

Long requested feature in Backpack Laravel-Backpack/community-forum#53

It's finally happening 🎉 🥳 🎈

It was possible, but difficult to implement email verification for registered users.

AFTER - What is happening after this PR?

It's dead simple as changing a config value, and all your admin routes will now require the verified email. 👍

HOW

How did you achieve that, in technical terms?

I've followed Laravel documentation and adapted to our use-case.

Is it a breaking change?

I don't think so,no. It's behind a config that's false by default.

How can we test the before & after?

Find the docs here: Laravel-Backpack/docs#503

This PR requires:
Laravel-Backpack/theme-tabler#142
Laravel-Backpack/theme-coreuiv2#32
Laravel-Backpack/theme-coreuiv4#48

NOTE TO SELF: update composer.json with CRUD version in those PR's before merging.

[tabacitu]

I love it! Well done @pxpm ! I've gone through all of the code thoroughly, but haven't tested this yet. I only have one concern - see in the inline comments.

When that is resolved, I think it's ready for testing and launch.

[tabacitu]

/gpt can you summarize the issue?

[github-actions]

@tabacitu The issue is a pull request that adds email confirmation functionality to the Laravel Backpack CRUD package. The pull request aims to make it easier to implement email verification for registered users by adding necessary middleware and controllers. The proposed changes include updating the BackpackServiceProvider to register the new middleware, updating the RegisterController to handle email verification, and adding a new VerifyEmailController to handle the verification process. There are discussions about whether this should be a responsibility of the main application or the package itself.

[tabacitu]

In a freshly set up demo, I've followed the steps in the docs, then registered a user. After registration, I've been sent to this page:

Note that:

(1) I am using the proper branches for all themes:

(2) The error page has the admin panel menu 😱 So I think it has already logged me in - but I haven't verified the email yet. Shouldn't we login only AFTER verification?

(3) Granted, what I did wrong was that I messed up a middleware name - I added it as verify instead of verified. If I hadn't done that, I probably wouldn't have seen this error page difference, so I wouldn't have a sneak peek of the menu without actually having the email address verified. But even if I trigger other errors while in this status (registered but not verified) I see the menu. For example if I trigger the email verification too many attempts. So I think the safest is to completely log in the user upon verification. NOT upon registration.

[tabacitu]

Heads-up, I added a PR to demo too - Laravel-Backpack/demo#571 - since I already had the code on my machine, following your docs.

[pxpm]

It makes sense. I've updted the PR's to account for that

[tabacitu]

I've given this a good hard look, how we can clean it up. Let me know.

[tabacitu]

I've given this another look. And another test. Looks & works good to me! WE HAVE IT. Let's do it, let's merge! 🎉🎉🎉