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
The way ERT evaluates complex types and language specific features is largely a manual process. We have to manually tell ERT how to interpret things like extends and React.FC<P>, so inevitably there will be things that we don't support or haven't considered.
This issue aims to track what features we do and don't support and in cases where a feature is unsupported, we hope to provide a suitable bail-out, similar to what is suggested here #141
If there's something missing on this list, please leave a comment below 😄
The way ERT evaluates complex types and language specific features is largely a manual process. We have to manually tell ERT how to interpret things like
extends
andReact.FC<P>
, so inevitably there will be things that we don't support or haven't considered.This issue aims to track what features we do and don't support and in cases where a feature is unsupported, we hope to provide a suitable bail-out, similar to what is suggested here #141
If there's something missing on this list, please leave a comment below 😄
TypeScript
boolean, array, string, number
✅any
✅unknown
✅void
✅array[]
&Array<>
✅type foo = string
✅'foo' | 'bar'
✅Foo & Bar
✅TypeScript utility types
Omit<>
❌Partial<>
❌Record<>
❌Pick<>
❌ReturnType<>
❌TypeScript via @types/react
React.FC<Props>
✅React.memo<Props>
✅React.forwardRef<ElementType, Props>
✅Flow
TBD
Related issues
#59
#141
The text was updated successfully, but these errors were encountered: