Should we move hie-plugin-api to its own repo?

[alanz]

hie-plugin-api provides a number of things, the most fundamental being an API that plugins can code against. This is used by HaRe. But HaRe is also used as a plugin in hie.

Since none of these is currently in hackage, we end up with the absurd situation where haskell-ide-engine has HaRe as a submodule, which in turn has haskell-ide-engine as a submodule, and on it goes.

Git knows how to do the right thing, but this is awkward and confusing.

A possible solution is to move hie-plugin-api to its own repo, which in the current development model would result in it being a submodule of haskell-ide-engine, and also of HaRe, but then without cycles.

Comments? Other solutions?

[lorenzo]

There is a big amount of friction in having things setup as separate repos. A small change such as adding a new Config value can end up in a long change of small steps that can slow down development.

I don't have a lot of experience with this but, can we maybe source the parts of Hare that depend on the haskell-ide-plugin inside this repo and separate them entirely from HaRe?