You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a model Shopping List Item. I've defined it as such:
import { Model } from '@vuex-orm/core';
export default class ShoppingListItem extends Model {
static entity = 'shopping_list_items';
static fields () {
return {
id: this.attr(null),
title: this.string(''),
checked: this.boolean(false),
quantity: this.number(0),
created_at: this.attr(null),
updated_at: this.attr(null),
};
}
}
When I attempt to run a $save() and $push(), I receive the error: Couldn't find Type of name Shopping_list_itemInput in the GraphQL Schema.
Theoretically I could change the name of the input on the backend to Shopping_list_itemInput, however I think you'll agree that this is not optimal. Do you have any suggestions for naming multi-worded models?
The text was updated successfully, but these errors were encountered:
Just to follow up here, I think I've found a suitable enough solution for my problem.
By changing the entity name and all relation references to camelCase, as well as references in the backend schema to camelCase, I am able to successfully avoid ugly mixtures of camel- and snake-case. So taking the above model in the original question, I changed to something like this:
And because the name of the input is derived from the getInputTypeName function of the DefaultAdapter class, this would change the input that it's searching for to ShoppingListItemInput.
Hi there, I've got an odd sort of question.
I have a model Shopping List Item. I've defined it as such:
When I attempt to run a
$save()
and$push()
, I receive the error:Couldn't find Type of name Shopping_list_itemInput in the GraphQL Schema
.Theoretically I could change the name of the input on the backend to
Shopping_list_itemInput
, however I think you'll agree that this is not optimal. Do you have any suggestions for naming multi-worded models?The text was updated successfully, but these errors were encountered: