While we already have a Data Access Object for handling Users, we should add additional data access objects for some of the other major entities that we are storing (Artists and Tracks) in order to keep in line with the SOLID principles (mainly the Single Responsibility Principle)
Your Changes
Description:
I created two new data access objects for the Artist and Track entities, which store a dictionary containing the ids and actual object values. This data will also be stored in a json file(Not Implemented Yet). This is done to prevent multiple users creating different Track objects for the same track, which also reduces the amount of API calls we shall be making. Also, added the save method to each of the data access objects to write the data to a json file (not implemented yet)
Type of change (select all that apply):
[x] New feature (non-breaking change which adds functionality)
[x] Refactoring (internal change to codebase, without changing functionality)
Testing
Questions and Comments (if applicable)
The methods that deal with reading and writing from the json files have not been implemented yet
Checklist
[x] I have performed a self-review of my own code.
[x] Coding style (conforms to Google Java Style Guide)
[x] Especially follows section 7 (Javadoc is present for every public class, public or protected member)
[x] Especially follows section 4.6 (Multiple consecutive blank lines are not encouraged)
[x] Correctness (follows CA and SOLID, is a reasonable and not overly complicated solution, etc.)
[x] Description of pull request is clear, consise, and reasonably detailed
Motivation and Context
While we already have a Data Access Object for handling Users, we should add additional data access objects for some of the other major entities that we are storing (Artists and Tracks) in order to keep in line with the SOLID principles (mainly the Single Responsibility Principle)
Your Changes
Description: I created two new data access objects for the Artist and Track entities, which store a dictionary containing the ids and actual object values. This data will also be stored in a json file(Not Implemented Yet). This is done to prevent multiple users creating different Track objects for the same track, which also reduces the amount of API calls we shall be making. Also, added the save method to each of the data access objects to write the data to a json file (not implemented yet)
Type of change (select all that apply):
Testing
Questions and Comments (if applicable)
The methods that deal with reading and writing from the json files have not been implemented yet
Checklist