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
This is causing issues with, for example, a third type Z:
typeZ {
theX: X
}
and in code
import{X}from"./types";functiongetTheX(): X{returnfetchY();// ^^^ Error since mapping of X to Y is not applied here (return type is declared to be X explicitly)}constZ: ZResolvers={theX: getTheX(),// ^^^ Error since X does not match remapped type Y}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Please help me understand why a remapped type
X
's definition is still generated from the schema instead of aliasing the mapping type.For example, given a type
X
:If
./y#Y
were declared as mapped type ofX
, thenX
should be printed asinstead of
This is causing issues with, for example, a third type
Z
:and in code
Instead, I now have to write this as
Beta Was this translation helpful? Give feedback.
All reactions