Fix ObjectType casing and conflict between Relation and RelationMetadata (#9849)
Fixes #9827 Also uncovered a conflict with `@objectType('Relation')` and `@objectType('relation)` I don't want to address it in this PR so I will create a followup issue when we close this but I think there's a confusion between Relation/RelationMetadata, it's unclear what is what --------- Co-authored-by: Antoine Moreaux <moreaux.antoine@gmail.com>
This commit is contained in:
@ -13,7 +13,7 @@ export const objectsMetadataFactory = ({
|
||||
input,
|
||||
}: ObjectsFactoryParams) => ({
|
||||
query: gql`
|
||||
query ObjectsMetadata($filter: objectFilter!, $paging: CursorPaging!) {
|
||||
query ObjectsMetadata($filter: ObjectFilter!, $paging: CursorPaging!) {
|
||||
objects(filter: $filter, paging: $paging) {
|
||||
edges {
|
||||
node {
|
||||
|
||||
@ -14,8 +14,8 @@ export const createOneRelationMetadataFactory = ({
|
||||
input,
|
||||
}: CreateOneRelationFactoryParams) => ({
|
||||
query: gql`
|
||||
mutation CreateOneRelationMetadata($input: CreateOneRelationInput!) {
|
||||
createOneRelation(input: $input) {
|
||||
mutation CreateOneRelationMetadata($input: CreateOneRelationMetadataInput!) {
|
||||
createOneRelationMetadata(input: $input) {
|
||||
${gqlFields}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user