You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, I think entity resolvers should be allowed on nested objects as long as these are singletons (so as long as the fields that lead to it don't take arguments). Not sure if we should allow @entityResolver (or whatever directive we land on) on types however, because the marker applies to individual fields. (Also, I'm assuming @internal on Query.persons is used here to hide the entity resolvers from the API schema, but you wouldn't generally want that because these fields are useful for clients as well.)
Do we want to allow entity resolvers that can be nested?
The text was updated successfully, but these errors were encountered: