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
When using typegraphql (but also would likely be an issue when nexus), when using noncount nouns or a resource that does not have a plural form (i.e. equipment) the queries for GET_LIST and GET_ONE will be the same thus causing a conflict.
typegraphql handles this by exporting these differently instead of having a singular equipment which would be duplicated, it names the queries differently:
findManyEquipment findUniqueEquipment
In this case, it would be somewhat easy to change the underlying query logic that is inside of the makeIntrospectionOptions to handle this based on the query dialect for now (which already exists). However, since other methods might exist it might be better to be able to pass in the query resolver name through the useDataProvider options.
Provide a way to override operation names to handle edge cases where the resource name is not the actual operation or the operations were customized
```
useDataProvider({
operationNames: {
RESOURCE_NAME: {
create: "myCreateOperation",
update: "myUpdateOperation",
delete: "myDeleteOperation",
one: "myOneOperation",
many: "myManyOperation"
}
}
});
```
When using typegraphql (but also would likely be an issue when nexus), when using noncount nouns or a resource that does not have a plural form (i.e.
equipment
) the queries forGET_LIST
andGET_ONE
will be the same thus causing a conflict.typegraphql handles this by exporting these differently instead of having a singular equipment which would be duplicated, it names the queries differently:
findManyEquipment
findUniqueEquipment
In this case, it would be somewhat easy to change the underlying query logic that is inside of the
makeIntrospectionOptions
to handle this based on the query dialect for now (which already exists). However, since other methods might exist it might be better to be able to pass in the query resolver name through theuseDataProvider
options.As an example:
The text was updated successfully, but these errors were encountered: