Introduction
This post is the first in a series of three posts that will understand how the MVC architecture works to create frontend ap...
For further actions, you may consider blocking this person and/or reporting abuse
I just stumbled upon your post and carefully studied your code. I think your code is well structured and organized, from the folder structure to the code itself. The namings are good that not even code documentation is needed. I enjoyed reading your code!
However, I would like to add some further thoughts to it. These are by no means criticism:
Userclass, the member functionuuidv4could be outsourced in order to use it for future use casesAnother remark is that the
idin theuserclass gets always re generated, even after reading an existing user from the local storage. So you can't rely on a particular user in this case.Awesome, thank you
You're welcome!
Thanks Carlos. Does the first and seconb post of this series could also apply for a Vue app instead of angular or would you change anything?
The second part is exactly equal in Vue and Angular. If there is very interesting, then I could to do a fourth part using Vue!
Thanks for your words!