`Type not found` when using HaxeFlixel

[tophattom]

`Type not found` when using HaxeFlixel

[AlexHaxe]

Haxe languageserver requires a .hxml file to know what classpaths, libraries and target to use when offering completion or other compiler services. lime projects use a project.xml file (because they need additional build options).
in VSCode lime extension bridges the gap, for other editors you will need to provide a .hxml file to make it work.

you might be able to point it to the .hxml file generated when building a lime project (e.g. <output>/<target>/haxe/debug.hxml). but that requires at least one lime build <target> and of course locks you into that specific target (for completion and compiler services).
switching to a different target is a click on a status bar text in VSCode, but without lime extension you will have to modify your LSP settings (I don't know if sublime allows per project LSP settings, so you might have to change your global settings everytime you change targets).

[tophattom]

Thanks for the info! I'll have to try out the debug.hxml you mentioned.

Can you describe how the Lime extension bridges the gap? I was wondering if something similar could be developed for Sublime. Or better yet, extend the Hate language server to maybe call lime to generate required configuration.

[AlexHaxe]

Can you describe how the Lime extension bridges the gap? I was wondering if something similar could be developed for Sublime.

see https://github.com/openfl/lime-vscode-extension

Or better yet, extend the Haxe language server to maybe call lime to generate required configuration.

I think that's a bit beyond the scope of Haxe languageserver.