How do you properly structure a repository class specifically to encapsulate all of your app's own API calls related to one particular given resource, such as orders or products?

A repository class properly encapsulates every single method genuinely related to fetching and manipulating one particular specific resource type, such as an OrderRepository containing methods like fetchOrders, createOrder, and cancelOrder, and this particular pattern keeps your actual networking specific code cleanly separated from the rest of your app's own UI and general business logic, meaning your widgets and other consuming code simply call a genuinely clear, well named repository method rather than needing to directly construct raw HTTP requests scattered throughout dozens of separate individual widgets.

class OrderRepository {
  Future<List<Order>> fetchOrders() async {
    final response = await dio.get('/orders');
    return (response.data as List).map((json) => Order.fromJson(json)).toList();
  }
}