replacem3nts / blankflix_api Goto Github PK

• User Controller: login, register, and persist_login actions should all call on the ChannelSerializer to set the state at the beginning of the session
• Movie Controller: add movie and update movie should both call on the ChannelSerializer to return an updated Channel object to add into state

Two options:

1. Has a find or create Channel that get's used every time a new ChannelMovie is created
2. Frontend has a list of Channels and crossreferences the list, if(exists) sends the channel id for a simple create ChannelModel function, if (doesn't exist) just sends movie id and Channel name to create a channel and ChannelMovie at the same time.

Should establish ActiveRecord relationships and provide basic validations such as presence and uniqueness of username, as well as has secure password for authentication.

• Channel (name:string)
• ChannelMovies (movie:foreign key, channel: foreign key)

Models to include:

• User (username, password digest, app_name)
• Movie (user_id, title, length, URL, cover_image)

Figure out if we need to use activeStorage or if we can pull a cover image thumb from YouTube API

• User Serializer
• Movie Serializer

-Should accept a user as an argument and return the channel name and an array of movie_ids
-Eric mentioned a method that takes two arrays and returns the overlap (maybe a sequel query or named scope)...
Structure of return:

Should reflect all the routes that have already been set up and rely on the serializers to format the outgoing json data

Should include:
USER

• Post User
• Patch User
• Delete User

MOVIE

• Post Movie
• Delete Movie

Basic user authentication using bcrypt, before actions, and the application controller.