list abstract method

Future<PaginatedRecords> list(String resourceKey, { int page, String? search, String? sort, String? direction, bool reorder, Map<String, Object?> filters, })

GET /{resource}

reorder: true switches to the full, unpaginated, reorder-ordered list — ?reorder=1 — and sort/direction are omitted from the request entirely, mirroring the server's own contract (P18): reorder mode discards the sort column outright, the same way Filament's own reorder-mode table does. search still applies in this mode.

filters (P24): name => String (single value) or List<String> (multiple). Encoded on the wire as INDEXED keys — filter[tags][0]=a&filter[tags][1]=b — never repeated ones (filter[tags][]=a&...). FilamentTransport.get hands the host a FLAT map, and the reference host stringifies every value (example/lib/http_filament_transport.dart), so a List<String> value would go out as the literal "[a, b]". Distinct indexed keys stay scalar strings — no change needed to the port or to any host — and PHP parses filter[tags][0]/filter[tags][1] into the same array filter[tags][] would have produced. The server accepts both forms; this client sends only the indexed one. Do not "simplify" this to repeated keys — that silently breaks multiple filters.

Implementation

Future<PaginatedRecords> list(
  String resourceKey, {
  int page,
  String? search,
  String? sort,
  String? direction,
  bool reorder,
  Map<String, Object?> filters,
});