Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Type-on-hover stops working inside components with more than one prop on OCaml 5.2 #840

Open
feihong opened this issue Jun 12, 2024 · 0 comments

Comments

@feihong
Copy link
Contributor

feihong commented Jun 12, 2024

Here's a small example:

[@react.component]
let make = (~foo, ~bar) => {
  <div> {React.string(foo)} {bar |> string_of_int |> React.string} </div>;
};

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:

let make ~foo  ~bar  =
  ((div ~children:[React.string foo; (bar |> string_of_int) |> React.string]
      ())
  [@JSX ]) [@@react.component ]

I created a small repo that demonstrates the problem: https://github.com/feihong/type-on-hover-bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant