View Code? Open in Web Editor
NEW
Items Catalog console app that will help you to keep a record of different types of things you own: books, music albums, movies, and games.
License: MIT License
catalog-of-things's People
Stargazers
catalog-of-things's Issues
Add a unit test for all the implemented methods in Book and Label classes.
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
Implement methods of Author class:
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 parent's method returns true AND if last_played_at is older than 2 years
otherwise, it should return false
Implement all methods of Gener Class:
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 parent's method returns true AND if on_spotify equals true
otherwise, it should return false
All data of Books and Lables should be preserved by saving collections in .json files.
Add a unit test for all the implemented methods in the Game and Author classes.
The following options should be available:
Create a Book class in a separate .rb file.
Create a Label class with an association to the Item 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 Label class properties visible in the diagram should be defined and set up in the constructor method.
Add a unit test for all the implemented methods in MusicAlbum and Genre classes.
Create an Item class in a separate .rb file.
All Item class properties visible in the UML class 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.
The following options should be available:
All data of MusicAlbum and Genre should be preserved by saving collections in .json files.
Create a Game class in a separate .rb file.
Create an Author class with an association to the Item class (in a separate .rb file).
All Game class properties visible in the diagram should be defined and set up in the constructor method.
All Author class properties visible in the diagram should be defined and set up in the constructor method.
Initiate a Project bundle init
Add linter configurations
Install basic dependencies gem, Rspec
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
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.
All data of Game and Author should be preserved by saving collections in .json files.
The following options should be available:
Implement all methods of Book Class:
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 parent's method returns true OR if cover_state equals to "bad"
otherwise, it should return 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 MusicAlbum class in a separate .rb file.
Create a Genre class with an association to the Item class (in a separate .rb file).
All MusicAlbum class properties visible in the diagram should be defined and set up in the constructor method.
All Genre class properties visible in the diagram should be defined and set up in the constructor method.
Implement archive 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