Skip to content
This repository has been archived by the owner on Nov 29, 2022. It is now read-only.

Refresh user object in frontend #201

Open
rhaamo opened this issue Oct 6, 2019 · 0 comments
Open

Refresh user object in frontend #201

rhaamo opened this issue Oct 6, 2019 · 0 comments
Labels
enhancement New feature or request Frontend This concerns the frontend
Milestone

Comments

@rhaamo
Copy link
Member

rhaamo commented Oct 6, 2019

After uploading or deleting tracks, the user object isn't refreshed, the quota won't change or track count, something needs to be done on that side.

Two things can be done:

  • Anything changing the content of a Track or User in the backend should returns a Track and/or User, that way it is going to be updated in the frontend (apiService might needs some edit)

  • Using the notifications timelime to push new User on it that would be updated, we don't have that timeline implemented in the backend however.

The latter needs to have a notification read implemented to avoid the timeline returning all objects every time.

@rhaamo rhaamo added enhancement New feature or request good first issue Good for newcomers labels Oct 6, 2019
@rhaamo rhaamo added this to the v0.5 milestone Oct 6, 2019
@rhaamo rhaamo added the Frontend This concerns the frontend label Oct 6, 2019
@rhaamo rhaamo removed the good first issue Good for newcomers label Nov 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request Frontend This concerns the frontend
Projects
None yet
Development

No branches or pull requests

1 participant