mattgomb / catalog-of-my-things

A console app that allows the user to keep a record of different types of things they owm: books, music albums, movies, and games. The project was created based on a UML class diagram. The data is stored in JSON files.

Hi 👋, I'm Matt

A future full-stack developer. Microverse alumni. A forever-curious weirdo.

• 🔭 I’m currently Looking for an opportunity

• 🌱 I’m currently learning React, TypeScript

• 👨‍💻 All of my projects are available at https://mattgomb.github.io/Portfolio-project/

• 📫 How to reach me [email protected]

• ⚡ Fun fact I like boardgames, tv-shows, and playing the guitar.

Connect with me:

Languages and Tools:

 

catalog-of-my-things's Issues

First review of the ruby capstone group project

Dear Reviewer,

Here is the link for our kanban board.

We assigned ourselves to each task, except for team member#3, because he has not accepted the invitation to the project yet, he is not in the call. But the tasks are assigned like this:

• Team member 1 is @jfoyarzo
• Team member 2 is @MattGomb
• (possible/probable) Team member 3 is @Dadadon

[1pt] Create database schema (tm2)

- 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

[3pt] Create MusicAlbum class (tm2)

• Create MusicAlbum class in a separate .rb file.

• Create 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 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

[1pt] Database tables (tm3)

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

[1pt] Create database tables (tm1)

• 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

[1pt] Create a main.rb (group)

- 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.

[1pt] Options in the menu (tm2)

• The following options should be available:
  • List all music albums
  • List all genres (e.g 'Comedy', 'Thriller')
  • Add a music album

[1pt] Add option to main.rb (tm1)

• The following options should be available:
  • List all books
  • List all labels (e.g. 'Gift', 'New')
  • Add a book

[1.5] Create Author class (tm3)

• 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.

• 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)

[1pt] Data preservation (tm3)

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

[1pt] Data preservation (tm2)

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

[1pt] Unit tests (tm1)

• Add unit tests for all implemented methods.

[1pt] Add options to main.rb file (tm3)

The following options should be available:

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

[1.5pt] Create Label class (tm1)

• 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 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)

[1.5pt] Create Book Class (tm1)

• 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.
• Implement methods:
  • can_be_archived?()
    • 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

[1pt] Create items.rb (group)

• Create 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.

• 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

[0.5pt] Add unit tests for MusicAlbum and genre methods (tm2)

All methods for music album and genre should be tested

[1.5pt] Create Game class (tm3)

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

• Implement methods:

  • 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

[1pt] Unit tests (tm3)

• Add unit tests for all implemented methods.

[1pt] Data preservation (tm1)

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