Specify unknown Type For Relational Field Resolvers In Generated Services
#5230
Conversation
When services are generated for models that have relations, Redwood generates field resolvers for those relations. This is very helpful, but defaults to showing alerts in a developer's editor for those lines of code. These alerts can be avoided by marking the type as `unknown`, since at the moment that's what it is, and allow users to add type definitions to the arguments if any arguments are added to the field in GraphQL.
✅ Deploy Preview for redwoodjs-docs canceled.
|
|
Thanks, @tubbo! Is there a prior conversation on Discord/Forums that provide some background here? (Fine if not.) Asking because I think we have several related things in motion about this right now — want to make sure they're all in sync. Looping in @jtoar @dthyresson |
No, it's just something I noticed I had to do every time I generated a new service object. Other than SDLs not generating their relations properly (which seems like a big chunk of work that's already been started, yay!) this is the only other gripe I have with Redwood's generators, that it generates code that causes alerts in my editor.
This was an epic troll because I clicked this link thinking it would go to the "several related things in motion". I tip my hat to you, sir. |
|
This PR won't be needed after #5216 👍🏻 |
haha! gotta get the fun going on a Monday! Also, what better way to welcome people to the community, right? 😂 |
When services are generated for models that have relations, Redwood generates field resolvers for those relations. This is very helpful, but defaults to showing alerts in a developer's editor for those lines of code on a TypeScript project. These alerts can be avoided by marking the type as
unknown, since at the moment that's what it is, and allow users to add type definitions to the arguments if any arguments are added to the field in GraphQL.