@igamingcareer/igaming-components 1.0.64 → 1.0.65

package/Readme.md

@@ -177,3 +177,30 @@ Key events include:
 - News Listing: search submissions/removals, filter select/clear/all-clear, date changes, category selection, pagination, view mode, items per page, article open/bookmark/share.
 
 When embedding via `renderMultiple` (see `src/main.tsx`), a global `window.IGC_EMIT_EVENT` handler will be passed automatically if present, along with a default context using the current route and optional `data-source` attribute.
+
+## Job Listing pagination-friendly API responses
+
+The `<Listing />` component now understands paginated API payloads. Set `apiProvidesPagination` (or the `data-api-pagination="true"` attribute when embedding) to tell the component your endpoint returns a `{ jobs: [], pagination: { page, limit, total, total_pages } }` envelope.
+
+- The component requests page `1` with `limit` set to the initial `itemsPerPage` value, reads the `pagination.total`/`total_pages` metadata, and then sequentially loads every remaining page to build the full `jobs[]` in memory.
+- While those pages are fetched, the UI stays in the loading state (using the first batch size for the skeleton), and once all pages are collected it serves the same client-side pagination experience as array-based responses.
+- If the flag is omitted, the component assumes a plain array response and paginates client-side as before.
+
+Example response shape:
+
+```json
+{
+  "jobs": [/* job objects for the current page */],
+  "pagination": {
+    "page": 1,
+    "limit": 5,
+    "total": 2284,
+    "total_pages": 457
+  },
+  "metadata": {
+    "cache_hit": false
+  }
+}
+```
+
+If your API still returns a plain array, leave `apiProvidesPagination` unset and the component will paginate client-side as before.