frontend-data

Create an APIService instance with window.appGlobal.baseUrl and the resource path matching the backend route, then call getAll, get, create, update, delete, or deleteAll. Each method returns a Promise of an AxiosResponse with the backend's data, meta, rels envelope.

Use the usePaginate composable with your APIService and a computed query object built from your filter refs. It watches the query and currentPage, re-fetches automatically on changes, and returns total, pages, response rows, and loading state.

The query passed to usePaginate must be a ref or computed, not a plain object, and its serialized value must actually change between updates. Check that v-model bindings match the filter property names and that empty strings are normalized to undefined.

Use useServerValidation's createUniqueValidator with the entity name, attribute name, and entityId when editing to ignore the current record. It calls /api/v2/core/validation/unique debounced by 500ms and returns true or a translated error string for the rules array.

The APIService response interceptor calls reloadPage on any 401, which redirects to the login page since the session is gone. You do not handle 401 manually; the interceptor also toasts unexpected errors automatically for other failures.

Call setIgnorePath with a regex matching validation endpoints where 400 or 422 responses are expected signals, such as uniqueness checks, to suppress automatic error toasts. The promise still rejects, so you must catch it yourself if you need to react.