Laravel Vue SPA Issue Tracker part 25: Vue email verification 

You're Welcome Bro

Thanks

I plan first to finish all the basic stuff on an application before going to something more specific. Thanks for watching!

My pleasure!

What next episode, after this

Well, after the verification email which was a request, I planned to start the admin too, to make at least one example of a CRUD functionality.

I barely heard about it but as fas as I know, it's not production ready, but it is a pretty interesting project that should be followed

Thanks for the support! Waiting for your requests, if you have!

@@ProgrammingwithPeter just a cart with vuex

obviously from the name of the project, we don't have any cart here, so it's going to be messy if we try to implement it, but can you elaborate more on what you need ? Maybe we can implement something really similar or create a separate video for this.

@@ProgrammingwithPeter obviously in separate video or git would do it

@@AhmadHassan-ss5un you can look at this /playlist?list=PL1TrjkMQ8UbVSDkDaLkjpeNGkblNU8rpW

You are back on track!

and token time control system with middleware

Hey man, I don't understand what you mean, so after the login to save something to localstorage and check in a middleware if we have it on database?

​@@ProgrammingwithPeter setLoggedInState () function does not checking localstorage token with database.

Oh, indeed, but that's because it has other purpose, setLoggedInState is just a front-end thing, we are going to make the auth more powerful soon, maybe on the next few episodes because we still don't logout when the token becomes invalid, as far as I remember! But we do save the token to localstorage and because after login we do /me, we can do the check there, if we can't get /me basically the token is not valid.

Yes, usually you need to implement db transactions, to rollback everything if something happens, on this case would be easy to do something like a try catch and delete the user or resend the email, but, on bigger features, db transactions is the way to do it. it also depends on your business logic ofc.

@@ProgrammingwithPeter I think it's easier not to write to the database if there was an error sending mail

on our simple case, yes.

wait, there is more to it, how you do that, because you still need to save the user and after that send the email, not reversed, so you need a way to not write to DB (all ways actually write something to the db, but it will delete it in case of error)

@@ProgrammingwithPeter Yes, I looked at how it is implemented in Laravel Auth - it is better to implement it somehow through resending