Custom API routing options.
Enable to serialize and deserialize records based on a shared logic
Adds an already existing target record to a relationship.
While waiting for real implementation (as compliant for JSON API spec) on the backend side, we are using a temporary solution requiring two API calls.
Elimina un record.
Version of fetchRequest integrated with transformRequest method, in
order to serialize the request body (if provided) and deserialize the
response, trasforming returned data into ModelRecord elements.
Scarica un singolo record
Load all records for a specific resource.
Scarica tutti gli elementi di una relazione per un determinato record.
Override this method in order to customize delete message.
Override this method in order to customize success message.
Removes a target element from a Relationship.
Resolve filters, removing empty ones.
Resolves includes, while checking (only first-level) if paths are present in model relationships definition.
Resolve pagination. Delegates to PagingStrategy
Resolve sorting, adopting JSON API specification.
Crea o Aggiorna un record in base al suo stato.
Modify request headers in order to add Authorization header.
Current record model
Parameters extracted from internal configuration status (auth, ecc.)
The target HTTP request
Generated using TypeDoc
Default API Client implementation that respects JSON API specification.
You can override the methods in order to handle specific models, when
Modelconfiguration is not enough.Elseway, you can use this Client implementation in order to write a custom implementation, i.e. to integrate into a GraphQL App or a local storage method.
Complete definitions