Referencing course ressources, here are my proposed classes and interfaces and overall structure for our project. I asked during an office hour where it'd be best to store our API directories and I was recommended in interface adapters. This way, we can build client interfaces where the use cases are calling for the requests from servers but won't know the low-level details about how or what the API is and how it's structured. THis way, it adheres to our dependency rule. Let me know what y'all think and if you have any other suggestions / recommendations.
There are also entities we should review now so that all our methods and API's expect the format when creating data access objects.
Referencing course ressources, here are my proposed classes and interfaces and overall structure for our project. I asked during an office hour where it'd be best to store our API directories and I was recommended in interface adapters. This way, we can build client interfaces where the use cases are calling for the requests from servers but won't know the low-level details about how or what the API is and how it's structured. THis way, it adheres to our dependency rule. Let me know what y'all think and if you have any other suggestions / recommendations.
There are also entities we should review now so that all our methods and API's expect the format when creating data access objects.