refactor(favorites)!: introduce favorites table with positioning #1367
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is the implementation of transforming the
User.Favoritesslice to a relational table that maps user_ids to repo_ids with positioning.This will allow for the UI to render user's favorite repos in their preferred order every time. Further, it prevents the issue of capping favorites at 5000 total characters.
This PR does not include the deprecation of the
User.Favoritesfield. That will be a follow up PR.Breaking Changes
New table
favorites, which will have to be created with data inserted from the existinguserstable. This will have to be addressed in the migration.Endpoints
POST /api/v1/user/favoritesGET /api/v1/user/favoritesPUT /api/v1/user/favorites/:org/:repoDELETE /api/v1/user/favorites/:org/:repo