Refactor the User Class

[k-allagbe]

Description

The User class, currently located in the datastore module, needs to be refactored. Specifically, the method get_user_container_client is not being called with the correct parameters.

Tasks

• Correct the parameters passed to the get_user_container_client method in the get_container_client function.
• Write tests for it's methods.
• Ensure all tests, including the newly added ones, pass successfully.

[Francois-Werbrouck]

What are the gains of making the User class into a pydantic model? (I'm not super familiar with pydantic)

[k-allagbe]

What are the gains of making the User class into a pydantic model? (I'm not super familiar with pydantic)

Doesn't have to be a pydantic model. I think its data is not even coming from db json so never mind that.

[Francois-Werbrouck]

Some of the data is coming from the DB.

However, we use a user class to make it easier for the BE to perform certain task based on the User's object/data.

We primarily use it to fetch the container_client of a specific user. This way, the BE doesn't need to know what is the implementation of this specific container. However, it is not always the user's container which is the destination of the upload (see this comment for more explanation)

The class could be expanded in the future to enable for more actions (ex: #172)

[k-allagbe]

Understood. Fixing the functions is enough in this case, strictly in the context of the present issue. Issue updated.

[Francois-Werbrouck]

Based on recent Discussion, this was mostly through the #224 Epic. I suggest to review the needs of this issue once the Epic finished