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
In VS Code, if you hover over foo or bar, you get (~foo: string, ~bar: int) => React.element, which is the type signature of the function. There are at least two ways to get normal type-on-hover back:
Remove one of the props, either foo or bar
Remove the [@react.component] attribute
Note that the problem isn't limited to Reason syntax, it also doesn't work with OCaml syntax:
Here's a small example:
In VS Code, if you hover over
foo
orbar
, you get(~foo: string, ~bar: int) => React.element
, which is the type signature of the function. There are at least two ways to get normal type-on-hover back:foo
orbar
[@react.component]
attributeNote that the problem isn't limited to Reason syntax, it also doesn't work with OCaml syntax:
I created a small repo that demonstrates the problem: https://github.com/feihong/type-on-hover-bug
The text was updated successfully, but these errors were encountered: