Get an introduction to app architecture and the repository pattern, then create the model classes for RWCourses.
This is a companion discussion topic for the original entry at https://www.raywenderlich.com/25841733-your-second-flutter-app/lessons/4
This is a companion discussion topic for the original entry at https://www.raywenderlich.com/25841733-your-second-flutter-app/lessons/4
I think that the name of repository abstract class should be different. What if we want to add more repositories in the future? The naming will be wrong, because repository interface is not created to be used by every repository implementation.
Personally I always stick with nameRepository for interface name and nameRepositoryImpl for class that implements that interface.