Open AntonioMrtz opened 3 months ago
Hi @AntonioMrtz. I saw your issue and I would like to contribute to project Would you assign this to me? :)
Hi @AlesSust , welcome to the project and thanks for your time. Sure, I will asign you to the issue. Let me know if you need anything :).We have a website with the project docs for set up the app and related topics. If you find this project interesting/helpful, I'd appreciate it if you could star the repo!
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.
Context
User class serves as BaseUser class and Artist inherits from it. The issue appears when trying to implement new users like for example an admin. This type of user doesnt care about fields such as
playback_history
and so.Currently User class is both a Base class and a Concrete one. This can lead to confusion because other inheritances in the app such as songs have a Base and Concrete class that are not the same.
The aim is to:
BaseUser
User
that inherits fromBaseUser
and its being inherited byArtists
.Watch below for more info about the attributes:
How to do it
BaseUser
User
Testing