[bug]: Required attributes are inferred as optional when generating types

[LuizPelegrini]

Bug Description

Moving issue from strapi/strapi repo

Attribute types for both Content-Types and Components are set as optional, even though they're marked as required when generating the types via strapi ts:generate-types command. The issue comes from the optional operator set it here and null type here

Steps to Reproduce

1. Clone this repo
2. Generate project types by running npm run strapi ts:generate-types
3. Update tsconfig to strict mode
4. Anywhere in your codebase, import Data type from @strapi/strapi
5. Create a variable and assign the type Data.ContentType<'api::post.post'> or Data.Entity<'api::post.post'>
6. Variable attributes are all optional

Expected Behavior

Required attributes should not be inferred as optional

Version

1.0.0

Operating System

MacOS

Runtime Environment

Node.js

Logs

No response

Media

Generated types

As you can see in the image, all fields (including required fields like title and seo) are set as optional.

Confirmation Checklist

• I have checked the existing issues
• I agree to follow this project's Code of Conduct
• I would like to work on this issue

[Convly]

Hello, thanks for opening this issue.

I'm sorry for the confusion but this is unfortunately not related to the SDK but to our core types.

As Derrick's said in the original issue, this is currently the intended behavior. However, this might lead us to think about how to expose both strict and non-strict versions of a document. (when we'll add the TS support for the SDK (which will allow using generated types from the Strapi apps))

I'm gonna close this one as it's currently not an SDK issue, but I've replied on the original one, happy to continue the discussion there or on our Discord.