How is the User entity usually implemented in the context of the Application User?

Question

Problem-Based Design

Greetings!

Tell me, what does the User class of most projects usually implement in itself? Where User is just a site user (admin, site visitor, authorized site visitor, etc.) who can read, write, delete, update data.
Does it have to do anything at all, or does it just act as a dumb store of value objects?
As I understand it, for example, for authorization, user registration, a service class is usually made that registers this user, authorizes, etc., since the User does not authorize or register himself.

And, if you know examples that could be useful to me (preferably in Typescript / JS), please give a link to Github.

Answer 1

Depends on business logic, application architecture, future plans for the application, needs of application users.
Here is an example of a simple user model implementation:
https://medium.com/javascript-in-plain-english/cre...