-
Notifications
You must be signed in to change notification settings - Fork 60
No hover type hint for variables #550
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
Comments
Make sure the file was saved before trying to hover. |
The file was saved. I did other trials
Then the hover hint appears.
3rd round:
Maybe the extension is not compatible with yarn 2? |
We have no windows devs, so these are always tricky. |
Can you try the pre-release version of the extension? |
nothing changes |
I tested it in wsl with yarn 2. NO hover hint still.
|
Before we have a fix, can you try https://github.com/reason-seoul/yarn-plugin-rescript and check if the extension works with that? |
@fhammerschmidt it seems to have issue, too. |
Ok, I guess the plugin is not compatible with Windows (or your setup). Alternatively: Then the extension should work without setting the binary path manually. However it disables pnp. |
@fhammerschmidt ah, that works |
Just to clarify: It does not make sense for the extension to support yarn PnP yet, when even the compiler does not: rescript-lang/rescript#3276 As soon as you add some dependencies, you will have all kinds of issues. |
Closing this since there's nothing actionable for us here for now. |
I think there should be a hint, e.g. greeting is string, but nothing poped up.
It can auto-complete

external
keyword as expected.Rescript compiler works properly.

I'm new to rescript and not sure I installed the extension properly. I use yarn 2 thus no
node_modules
in the working directory, and find executables in.yarn
subdirectory.vscode
setting.json
:bsconfig.json
:package.json
:System info:
版本: 1.70.1 (user setup)
提交: 6d9b74a70ca9c7733b29f0456fd8195364076dda
日期: 2022-08-10T06:08:33.642Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 10.0.19044
extension version: v1.4.2
The text was updated successfully, but these errors were encountered: