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
Open ./ember-primitives/src/components/popover.gts
Expected behavior:
The import import { Velcro } from 'ember-velcro'; should show as used, as it is used in the component template at line 216.
Actual behavior:
The import import { Velcro } from 'ember-velcro'; shows as unused
Reproduces how often:
This can always be reproduced
Versions
IntelliJ IDEA 2023.3.2 (Ultimate Edition)
Build #IU-233.13135.103, built on December 20, 2023
Plugin version: 2023.3.1
Additional Information
The fields on the |velcro| value yielded from the <Velcro> component also are unresolved, could this be related to the issue itself or should this be considered to be another bug?
The text was updated successfully, but these errors were encountered:
It is probably related. Or it's an issue with intellij lsp not giving me any references anymore...
When you ctrl+click on the <Velcro tag, does it jump to the definition or import?
It is probably related. Or it's an issue with intellij lsp not giving me any references anymore... When you ctrl+click on the <Velcro tag, does it jump to the definition or import?
When I ctrl + click on the tag, the editor jumps to the import. That part seems to be working correctly
Description
When importing from a GTS file, IntelliJ reports the import as unresolvable.
This also causes the imported values to not have their types known.
Steps to Reproduce
./ember-primitives/src/components/popover.gts
Expected behavior:
The import
import { Velcro } from 'ember-velcro';
should show as used, as it is used in the component template at line 216.Actual behavior:
The import
import { Velcro } from 'ember-velcro';
shows as unusedReproduces how often:
This can always be reproduced
Versions
IntelliJ IDEA 2023.3.2 (Ultimate Edition)
Build #IU-233.13135.103, built on December 20, 2023
Plugin version: 2023.3.1
Additional Information
The fields on the
|velcro|
value yielded from the<Velcro>
component also are unresolved, could this be related to the issue itself or should this be considered to be another bug?The text was updated successfully, but these errors were encountered: