#159: Differentiate Between BaseUser and User

[AlesSust]

Description

Differentiate between BaseUser and User by creating a Base class for all users and a User class that implements it, just like Artist is doing it at the moment.

Commit type

• refactor: refactoring production code, eg. renaming a variable.

Issue

#159

Solution

The solution involves restructuring the User class hierarchy by creating a new BaseUser class to serve as a common base for all user types. The User class now extends BaseUser, aligning with the existing structure of the Artist class.

Proposed Changes

-created BaseUser
-modified User to inherit from BaseUser
-changed type annotations from User to BaseUser

Potential Impact

This change could affect any existing functionality that directly references the User class. Potential risks include compatibility issues in methods expecting a User instance but now receiving BaseUser. Careful testing and updates to type annotations will be essential to minimize side effects.

Additional Tasks

• Update documentation to reflect the new BaseUser and User class structure.
• Add tests for BaseUser and User to verify that inheritance and functionality work as expected.
• Update any dependencies or services that rely on the User class to use BaseUser where applicable.

Assigned

@AntonioMrtz

[AlesSust]

Still need to add:
-tests
-improve coverage