hafiz1379 / catalog-of-my-things Goto Github PK

Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:

• Games table (add all properties and associations from the parent Item class as table columns)
• Authors table

• Enhance the look and feel of the Ruby CLI App.
  • You can use tools like Colorize. 🎨

Implement methods:

• add_item method in the Genre class

• Should take an instance of the Item class as an input

• Should add the input item to the collection of items

• Should add self as a property of the item object (by using the correct setter from the item object)

• can_be_archived?() in the MusicAlbum class

• Should override the method from the parent class

• Should return true if the parent's method returns true AND if on_spotify equals true

• Otherwise, it should return false

• Create a Genre class with an association to the Item class (in a separate.rb file).
• All Genre class properties visible in the diagram should be defined and set up in the constructor method.

-Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:

• Music_albums table (add all properties and associations from the parent Item class as table columns)
• Genres table

This is the setup of our work

You can find the GitHub project https://github.com/users/hafiz1379/projects/4/views/1

There are 3 people in this group:

1. https://github.com/hafiz1379
2. https://github.com/JuanDiegoGuerra
3. https://github.com/Rysth

Implement methods:

• add_item method in the Label class

• Should take an instance of the Item class as an input

• Should add the input item to the collection of items

• Should add self as a property of the item object (by using the correct setter from the item object)

• can_be_archived?() in the Book class

• Should override the method from the parent class

• Should return true if the parent's method returns true OR if cover_state equals to "bad"

• Otherwise, it should return false

Create a main.rb file that will serve as your console app entry-point.

Implement startup actions:

• Present the user with a list of options to perform.
• Let users choose an option.
• If needed, ask for parameters for the option.
• Have a way to quit the app.

The following options should be available:

• List all books
• List all labels (e.g. 'Gift', 'New')
• Add a book

• Complete the schema.sql file with tables that will be analogical to the structure of the classes that you created.
• Also add the pertinent code to create the main database that will contain all tables created in previus tasks.

• All data should be preserved by saving collections in .json files.

The following options should be available:

• List of games
• List all authors (e.g. 'Stephen King')
• Add a game

• Add unit tests for all implemented methods.

• Create an Author class with an association to the Item class (in a separate .rb file).
• All Author class properties visible in the diagram should be defined and set up in the constructor method.

• Create a Game class in a separate .rb file.
• All Game class properties visible in the diagram should be defined and set up in the constructor method.

-The following options should be available:

• List all music albums
• List all genres (e.g 'Comedy', 'Thriller')
• Add a music album

• Add unit tests for all implemented methods.

• Create a Book class in a separate .rb file.
• All Book class properties visible in the diagram should be defined and set up in the constructor method.

• All data should be preserved by saving collections in .json files.

• All data should be preserved by saving collections in .json files.

• Create a Game class in a separate .rb file.
• All Game class properties visible in the diagram should be defined and set up in the constructor method.

• Add all methods visible in the diagram

Implement methods:

• can_be_archived?() in the Item class

• should return true if published_date is older than 10 years

• Otherwise, it should return false

• move_to_archive() in the Item class

• Should reuse can_be_archived?() method

• Should change the archived property to true if the result of the can_be_archived?() method is true

• Should do nothing if the result of the can_be_archived?() method is false

Create a schema.sql file with tables that will be analogical to the structure of the classes that you created:

• Books table (add all properties and associations from the parent Item class as table columns)
• Labels table

• Create a Label class with an association to the Item class (in a separate .rb file).
• All Label class properties visible in the diagram should be defined and set up in the constructor method.

Implement methods:

• add_item method in the Author class

• Should take an instance of the Item class as an input

• Should add the input item to the collection of items

• Should add self as a property of the item object (by using the correct setter from the item object)

• can_be_archived?() in the Game class

• Should override the method from the parent class

• Should return true if the parent's method returns true AND if last_played_at is older than 2 years

• Otherwise, it should return false

Create an Item class in a separate .rb file.

All Item class properties visible in the diagram should be defined and set up in the constructor method.

Exception: Properties for the 1-to-many relationships should NOT be set in the constructor method. Instead, they should have a custom setter method created.

• Create MusicAlbum class in a separate.rb file.
• All MusicAlbum class properties visible in the diagram should be defined and set up in the constructor method.

• Add unit tests for all implemented methods.