Create / update record not transformed to JSON:API format

[yoelpc4]

Hi nice plugin btw with JSON:API.

I wonder about way to creating/updating record on
https://github.com/scalient/vuex-orm-json-api/blame/master/README.md#L39-L40

Seems the data parameter is not formatted as described on creating spec and updating spec.

Your restful actions mixin only provides the raw data instead of JSON:API formatted to the json api request on

vuex-orm-json-api/src/mixins/RestfulActionsMixin.js

Lines 18 to 32 in db520b9

	/*
	* The Rails-y REST `create` action.
	*/
	async create(data = {}, config = {}) {
	return this.post(this.restResourcePath(), data, {multiplicity: "one", ...config});
	},
	/*
	* The Rails-y REST `update` action.
	*/
	async update(id, data = {}, config = {}) {
	// The JSON:API specification seems to prefer `PATCH` over `PUT`: See
	// `https://jsonapi.org/format/#crud-updating-resource-relationships`.
	return this.patch(this.restResourcePath(id), data, {id, multiplicity: "one", ...config});
	},

Can you help me with data request transformer when creating/updating record that comply to JSON:API spec?

[ZachPerkitny]

I'm having the same issue

[carsomyr]

Hi all, here's the way I see it: vuex-orm-json-api is meant for taking strings in the form of JSON:API documents from the network and transforming it into something semantically richer in the form of Vuex ORM records. Going in the other direction, it's just writing strings to the network to a server than can respond in whichever way it likes. When you write

User.jsonApi().create({name: 'Harry Bovik', items: {}});

where items is an association on User, how is that much more raw-er than a more formal approach (like how Rails handles nested associations as nested forms and fields_for)?

[AidanDaniel97]

We had a similar issue - for us, we are using a library in Laravel for handling JSON:API spec requests/responses so any request has to also be in the correct format or the server will respond with 401 as it's a bad request.

Any relational data can't be directly in the data property, or in the data.attributes property and must instead be under it's own data.relationships property alongside attributes. It also requires a 'type' property too.

We wrote our own transformer for this. The transformer checks against the model you're requesting on and sets the 'type' to whatever is defined in the model's entity method. It then gets a list of the fields defined in the model, and returns only the ones that are relationship fields such as HasOne, BelongsTo, HasMany .... We then check each property in the data being sent through the transformer, and if it's key is one of the relationship fields we put that in data.relationships. If it's not, it goes into data.attributes.

We also have a check for the BelongsTo relationship as this requires the relationship to be an object instead of an array. (We are still testing this with our system and different relationships might need to be added to this but my knowledge on these relationships is still fresh)

[bytebrain]

I fixed it by using this package to transform/serialize the model before posting: https://github.com/SeyZ/jsonapi-serializer
It works with all relations too. Just check all config options.