mrichar1
commented
9 months ago pinia-jsonapi expects to be handed an api object which behaves like axios - however it's agnostic as to what library you actually use. It should therefore be possible to map ofetch properties and functions onto axios equivalents so that they behave the same as far as pinia-jsonapi is concerned.
I've not thoroughly tested it, but creating an api function as follows instead of using axios seems to work as expected:
import { ofetch } from "ofetch";
const baseURL = 'https://example.com'
// 'req' contains a subset of axios configuration properties: https://axios-http.com/docs/req_config
const api = async (req) => {
// Construct the URL
let url = `${baseURL}/${req.url}`
// Construct the ofetch config
let oCfg = {
headers: {
'Content-Type': 'application/vnd.api+json',
Accept: 'application/vnd.api+json',
},
method: req.method,
params: req.params,
parseResponse: JSON.parse,
}
// Add body if data is defined (POST/PATCH)
if ('data' in req) {
oCfg.body = req.data
}
let result = await ofetch(url, oCfg)
// axios returns JSON nested under 'data' property.
return { data: result }
}I'd be interested to know if this works for you, or if you find any problems with it, as it would be good to formally support other clients including fetch, which should be manageable in the same way.
If this works I can look at creating an api instance 'map' which has working examples for different clients.
mdrews21
Is there a way to support ofetch client rather than using axios, since axios is not natively supported in Nuxt 3 anymore. Using axios anyways result in authentication problems in nuxt. Thank You!