Error: Field "Query.news" can only be defined once.

[jonybekov]

Describe the bug
I've created new content type called 'news'. Everything was working till I installed graphQL. When I installed graphQL server stopped working and showing this error:
Error: Field "Query.news" can only be defined once.
Here's complete log.
C:\Users\Acer\AppData\Roaming\npm-cache_logs\2019-10-18T16_17_21_355Z-debug.log

Screenshots

System

• Node.js version: v10.15.0
• NPM version: 6.4.1
• Strapi version: 3.0.0 -beta
• Database: GraphQL
• Operating system: Windows 10

[alexandrebodin]

Hi, can you share your api models plz ?

[jonybekov]

Hi, can you share your api models plz ?

Hi, yes of course.

[alexandrebodin]

Here is the explanation.

Your content type as a plural name. When we generate the graphql schema for the content type we generate a plural name based on the name of the content type to generate a query to get the list of entry.
Unfortunatly news is already plural so we create the same name for both the single fetch and the collection fetch. It produces this
example

type Query {
  news(id: ID): News!
  news(limit: Int, ...): [News!]!
}

This explains the error.

We should check that to avoid the issue in the future. For now you will have to rename your content type to be sth la NewsPost

Hope this helpes you :)

[jonybekov]

Here is the explanation.

Your content type as a plural name. When we generate the graphql schema for the content type we generate a plural name based on the name of the content type to generate a query to get the list of entry.
Unfortunatly news is already plural so we create the same name for both the single fetch and the collection fetch. It produces this
example

type Query {
  news(id: ID): News!
  news(limit: Int, ...): [News!]!
}

This explains the error.

We should check that to avoid the issue in the future. For now you will have to rename your content type to be sth la NewsPost

Hope this helpes you :)

It's working now. thank you so much!

[davidkhierl]

having also the same error with the content type of 'agenda'

[lerototi]

@davidkhierl Are you fixed it? I have a "anamnese" model, with this problem!

[lauriejim]

This issue comes from a plural issue. There is another issue open about it.
Try to fix it by using @alexandrebodin fix.

[norbertbede]

hi. same here
v. 3.0.0-beta.17.8 (node v10.13.0)

[JKortmann]

I have the same error.
3.0.0-beta.17.8 (node v13.1.0)

[jared-shepherd]

In case anyone happens upon this post as I did and it doesn't resolve their issue, this might help!

I was creating components in 3.0.4 and Strapi crashed with this message:

There can be only one type named "editComponentGroupNameComponentName"

The solutions was to delete a duplicate JSON file at this location: ./components/GroupName/ComponentName.json

[sebastianjung]

As I do not need the news model available on my graphql endpoint i disabled the shadow crud creation of the news model like so (inside the api//config/schema.graphql.js)

module.exports = {
  resolver: {
    Query: {
      news: false // The `news` query will no longer be in the GraphQL schema.
    }
  },
};

which makes the error disappear. Most of you might need to rename the model though. Just my specific case i wanted to share.

Read more about disabling the shadow crud feature here:
https://strapi.io/documentation/v3.x/plugins/graphql.html#customize-the-graphql-schema

[derrickmehaffy]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/error-field-query-products-can-only-be-defined-once/2393/1

[orszaczky]

Why is this closed? It's obviously still an issue. My installation broke because of this - I created two nested components (resources, and repeatable called resource), and my app crashed. I tried to fix it manually and now my admin UI doesn't load anymore.

This issue and the allowed naming patterns should be documented and there should be a warning at component creation about what namings are allowed. :/

[derrickmehaffy]

It's closed due to: #4289 (comment)

The parent issue for this: #1198

Locking thread, comments about words that aren't handled should be pointed to the parent issue.