When I for example have a reference paragraph field with unlimited amount of items it creates a ParagraphUnion field, I get that but in Drupal we have the option to select what paragraphs we want for that field. Wouldn't it be better if we create separate unions based on the allowed paragraphs/content types/terms for that certain field? This would make our schema more type-safe. And creating separate unions for each field could make the schema more explicit about what types are allowed in each field. This could be helpful for frontend developers consuming the API.
I get that the schema would become more complex and maybe therefor this way of creating Unions is chosen. But might be something to look into.
Active
2.3
Code
Yeah, from memory we added a simple/complex option in the schema settings to do just that.
It’ll bust out entry refs into unique unions.
Wow, no idea how I didn't see that. That's exactly what we needed. Thanks