When you create a required field, the schema should reflect that and make the corresponding GraphQL field non-nullable . Using TypeScript with all the fields being nullable forces you to extensively narrow-type everything or use optional chaining where you might not want to. This could be accompani…

Hey everyone, we finally made it! :tada: :tada: :tada: We just shipped a new X-Exclude-Invalid header that you can add to change the GraphQL types of required fields: [image] API endpoint and header modes Discover DatoCMS, our headless CMS for websites of any size. …

@s.verna I can see that you’ve voted for this feature request; would you be able to give us any insight into what blockers (if any) exist to implement this, and if possible, a rough level of effort on your end? I’m just wanting to understand if this would be something that could be implemented relat…

The problem is that, even for required fields, the value of a field might be null. Counterintuitive, I know. Suppose you have a model Article, create a bunch of article records, and THEN add a new (required) field. In this case, the value for such field in already existing records will be null de…

@s.verna thanks for the detailed explanation, makes sense! I guess adding allValidX + validX query patterns likely wouldn’t be viable, because that would introduce the potential for naming collisions (for example, if there were models called both X and validX). Also, doing so would double the amoun…

Correct, a new endpoint was also my conclusion. It’s a bit of work, so we need to book some time for that. We don’t have an ETA yet :roll_eyes:

This would be an amazing addition to Dato. GQL + TS + Codegen is an amazing combination that massively boosts developer productivity but sadly cannot be used to its fullest in the current setup. Have you already had a chance to scope this feature?

Uh, we just went through the effort of enabling strictNullChecks and now I find this. Littering the code with unnecessary null checks makes everything feel fragile. :cold_sweat:

[image] I’ve just pulled our latest code-generated schema and noticed some are now Non-Nullable. @s.verna did you ship and update to this? @joealden have you found this?

Yes, we could change some types to non-nullable even in the current endpoints… but for the complete removal of Maybe types on required fields we still need to build a special endpoint that only returns valid records!

So it’s basically the default fields and array types now? That certainly helps! I’m not familiar with what’s possible on a GraphQL schema but could there be some way to include info on the type if a field is required or not? This would allow creating a type guard function to check if a record is va…

Make required fields non-nullable in GraphQL schema

✋ Feature Requests

mat_jack1 March 16, 2022, 11:23am 11

let’s keep in mind the votes on this request: Improve GraphQL Schema for required fields that was a duplicate

Topic		Replies	Views
Improve GraphQL Schema for required fields ✋ Feature Requests cda	7	1937	June 10, 2022
Structured Text with Typescript 🆘 Support	8	1610	June 12, 2024
Required field for localized content 🆘 Support	5	1105	February 13, 2020
Set a fallback locale ✋ Feature Requests launched , cma , localization	15	3929	February 18, 2022
Graphql-codegen typescript types for ImgixParams are too strict 🆘 Support	3	697	July 12, 2022

Make required fields non-nullable in GraphQL schema

Related topics