Setting module path seems not to work?
vantreeseba opened this issue · comments
It seems like everything but completion is working.
It seems like everything but completion is working.
Yeah that does seem like the issue I was having too.
Can you attach the coc log or the info if there are errors occuring?
I can't do that atm, sorry. Will do later if it still helps, but seems like you managed to reproduce
Ok, thanks!
Yeah if we're having the same symptoms then don't worry about logs.
For myself, this seems to be related to something in the haxe language server, not sure why this is occuring, but reverting to 0.4.0 with the bin at the point everything works fine.
Do you know from which version of haxe lsp this one was from?
0.4.0 was publish on June 4, so I did pull a lsp commit from before then and it worked fine, so I'm assuming there is some change since that works fine with vscode but coc isn't dealing with in the same way.
Ok, I'll try to find the commit you used and what changed since then.
Do you mind if the process to write bin/server.js changes so that it's easier to know where it's from and to update it? There's already a build process anyway :)
How did you build it? I fail to get a similar output =/
I'm down for anything with a pull-request, atm I build the bin/server.js by hand and copy it over from LSP.
The build steps are on their repo (i.e. the lix stuff).
I'm not 100% sure what you mean by
Do you mind if the process to write bin/server.js changes so that it's easier to know where it's from and to update it? There's already a build process anyway :)
Do you mean when I commit those changes, add something to the comment marking what commit of the LSP repo it came from or etc?