HaxeFoundation / HaxeFoundation/haxe
[display] import diagnostics should take type parameters into account
Open
enhancement
feature-ide
- Dominant language
- Haxe
- Stars
- 6.9k
- Forks
- 715
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 11
Description
In this case, a type whose type parameters don't fit is suggested as the preferred choice, so applying the quick fix is then followed by an "invalid number of type parameters" error. This is especially annoying because of VSCode's new "auto fix" command / preferred code action API.

If possible, type parameters should be taken into account to sort accordingly from "best" to "worst" fit.
Contributor guide
Assessment
This issue has not been assessed yet.