Project Catalog my things

[imranhossainemi]

Project Update

1.Team member # 1 - Imran Hossain

• 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.
• 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 parent's method returns true OR if cover_state equals to "bad"
• otherwise, it should return false
• Add unit tests for all implemented methods.
• The following options should be available:
• List all books
• List all labels (e.g. 'Gift', 'New')
• Add a book
• All data should be preserved by saving collections in .json files.
• 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

2. Team member # 2 Santosh Konappanavar

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

• Add unit tests for all implemented methods.

• The following options should be available:

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

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

• 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

3. Team Member # 3 Ikoote Rasuli

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

  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 parent's method returns true AND if last_played_at is older than 2 years
• otherwise, it should return false
• Add unit tests for all implemented methods.

  The following options should be available:

• List of games
• List all authors (e.g. 'Stephen King')
• Add a game
• All data should be preserved by saving collections in .json files.
• 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

[NahnahAJ]

Project Status: INVALIDATED :red_circle:

Hi @imranhossainemi , @ikoote1 and @Santosh-Konappanavar ,

While you made a great effort in this project, I can't go ahead and review your code.

Invalid Code Review Request

• This is because you have submitted a project, that needs to be submitted for the external or final review with a PR created from the development branch merging into the main branch. This was communicated to you in this article: https://github.com/microverseinc/curriculum-transversal-skills/blob/main/code-review/articles/code_review_flow_group_projects.md .
• So kindly submit a new PR following the right GitFlow :+1:

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏

Cheers, and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me @NahnahAJ in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

---

Invalid Code Review Request does not count into the code reviews limit.