Make generated graphql entity non optional

[msadegh76]

fixes #11815

What does it do?

It makes the "EntityResponseCollection" and "id" and "attributes" key of generated graphql "Entity" non optional.

Why is it needed?

Working with typescript in Strapi is tedious because the aforementioned attributes/types are marked as optional.

The code requires a number of type assertions or optional chaining constructs to eliminate the undefined/null types leading to obscure and hard to read code.

How to test it?

In Strapi create a simple content type with two non-optional attributes, namely 'title' and 'description'.

The currently generated Schema portion looks as follows:

// Current generated schema portion

type Post {
  title: String!
  description: String!
  createdAt: DateTime
  updatedAt: DateTime
  publishedAt: DateTime
}

type PostEntity {
  id: ID
  attributes: Post
}

type PostEntityResponse {
  data: PostEntity
}

type PostEntityResponseCollection {
  data: [PostEntity!]!
  meta: ResponseCollectionMeta!
}

After applying this patch the schema will instead contain the following types:

// Desired generated schema portion

type Post {
  title: String!
  description: String!
  createdAt: DateTime
  updatedAt: DateTime
  publishedAt: DateTime
}

type PostEntity {
  id: ID!
  attributes: Post!
}

type PostEntityResponse {
  data: PostEntity!
}

type PostEntityResponseCollection {
  data: [PostEntity!]!
  meta: ResponseCollectionMeta!
}

Related issue(s)/PR(s)

#9411

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
contributor-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 1, 2024 2:41pm

[strapi-cla]

All committers have signed the CLA.