getStanConfig is the only essential one for the plugin. I factored-out the second getAnalysis to use it as-is for hls. However, that is not possible because all the internal machinery in stan works with only relative paths, while the plugin at the end requires an absolute path. I'm inclined to leave it as is, but if it were possible to change stan internals to get one version of the function with both the plugin and stan itself, that would be nicer.
This also exports runStan, but it would be no problem leaving it there.
This is no much more than anything a separation of functions, so that
stan
functionality can be better added to thehls-stan-plugin
(https://github.com/haskell/haskell-language-server/pull/3914).getStanConfig
is the only essential one for the plugin. I factored-out the secondgetAnalysis
to use it as-is forhls
. However, that is not possible because all the internal machinery instan
works with only relative paths, while the plugin at the end requires an absolute path. I'm inclined to leave it as is, but if it were possible to changestan
internals to get one version of the function with both the plugin andstan
itself, that would be nicer.This also exports
runStan
, but it would be no problem leaving it there.