Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibly move user display name fetch to backend #38

Open
Noam-Bendelac opened this issue Mar 17, 2020 · 1 comment
Open

Possibly move user display name fetch to backend #38

Noam-Bendelac opened this issue Mar 17, 2020 · 1 comment
Labels
backend Backend functionality implementation Possible implementation idea to keep in mind

Comments

@Noam-Bendelac
Copy link
Collaborator

Make the /api/playlists/:playlistId/ backend endpoint do more (fetching added_by user data for display name), and have the frontend be simpler? Considering the question of small atomic endpoints versus more complicated endpoints that provide all the data the user needs: I'm already going to bundle the Spotify request with the database, so it might make sense to add this functionality too.

@Noam-Bendelac Noam-Bendelac added the implementation Possible implementation idea to keep in mind label Mar 17, 2020
@Noam-Bendelac Noam-Bendelac added this to the First user study milestone Mar 17, 2020
@Noam-Bendelac Noam-Bendelac added the backend Backend functionality label Mar 29, 2020
@Noam-Bendelac
Copy link
Collaborator Author

Need to add a cache of user id -> display name with TTL in the backend for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend functionality implementation Possible implementation idea to keep in mind
Projects
None yet
Development

No branches or pull requests

1 participant