hilla icon indicating copy to clipboard operation
hilla copied to clipboard

VS Code does not suggest imports for signals in a new project

Open Legioth opened this issue 1 year ago • 0 comments

Describe the bug

VS Code does not suggest imports for e.g. signal or useSignal in a new Hilla project.

This changes if you add e.g. import { signal } from "@vaadin/hilla-react-signals" in any file. Once that line is present somewhere, then VS Code will suggest imports for e.g. useSignal also in other files. If you again remove all imports for the module, then it will again not suggest any imports.

Expected-behavior

Expected auto completion for signal and useSignal in all cases.

Reproduction

  1. https://github.com/Lodin/hilla-file-router-example/commit/ec8cd0b6f580f052292082ea598702c49f30d0df
  2. Open $index.ts and write const x = signal(0) somewhere in the file.
  3. Open the Quick Fix menu and observe that there's no suggestion to import signal.

System Info

Vaadin 24.4.0.alpha7

Legioth avatar Mar 01 '24 08:03 Legioth