You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I really liked the architecture used in this project, I just have a couple of questions I was hoping you could answer me.
In many places you use type(of: self) to access static constants, whats the reason or advantage to declare those as static and not just a let?
At the ItunesWebService class you parse the data you receive from the request, but you are accessing the data through key value. Any reasons to not be using Encoding/Decoding? And if it could be used, how would it work?
You only have one entity AppData, in a more complex application would you have many entities? For example, a User entity, Product entity, Department entity, etc. And if so, would this cause any major changes in any part of the structure?
The text was updated successfully, but these errors were encountered:
Hi, I really liked the architecture used in this project, I just have a couple of questions I was hoping you could answer me.
In many places you use
type(of: self)
to access static constants, whats the reason or advantage to declare those as static and not just alet
?At the
ItunesWebService
class you parse the data you receive from the request, but you are accessing the data through key value. Any reasons to not be usingEncoding/Decoding
? And if it could be used, how would it work?You only have one entity
AppData
, in a more complex application would you have many entities? For example, a User entity, Product entity, Department entity, etc. And if so, would this cause any major changes in any part of the structure?The text was updated successfully, but these errors were encountered: