Jens Fischer
Jens Fischer
To ease the transition between Haxe 3 and 4, it would be nice to have code actions for the following: - [ ] replace `@:enum abstract` with `enum abstract` -...
 The best / simplest fix might be to simply change the range reported by Haxe.
Original issue: https://github.com/vshaxe/haxe-languageserver/issues/13 Two things from there are still missing: - [ ] a code action to import a static field from a class - [ ] a code action...
Like here for TS: https://twitter.com/mattbierner/status/1021496804330950656 Should be doable with the existing info that Haxe sends us.
It would be quite cool to have potential static extension functions appear in completion, even if there's not a `using` for them yet. If selected from completion, the `using` would...
Original issue: https://github.com/vshaxe/haxe-languageserver/issues/29 There is at least one situation where the completion server can hang due to a Haxe bug (meaning no more completion until VSCode or the language server...
It feels a little counter-intuitive to me that the import quick-fix only shows up after a save - at first I thought it wasn't working. Could we detect if there's...
see HaxeFoundation/haxe#4699 - Haxe 4 removes support for the old Haxe 2 style property syntax, so trying to compile Nape with it leads to a bunch of errors: ``` C:/HaxeToolkit/haxe/lib/nape/2,0,20/nape/geom/Vec2.hx:641:...
``` haxe package; import nape.callbacks.CbType; class Main { public static var cb = new CbType(); public static function main() {} } ``` ``` haxe -main Main -lib nape -neko run.n...
Exact same issue as described here for a similar extension: https://github.com/d4rkr00t/vscode-open-in-github/issues/9