Open alanz opened 5 years ago
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
?
hie-plugin-api
provides a number of things, the most fundamental being an API that plugins can code against. This is used by HaRe. ButHaRe
is also used as a plugin inhie
.Since none of these is currently in hackage, we end up with the absurd situation where
haskell-ide-engine
hasHaRe
as a submodule, which in turn hashaskell-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 ofhaskell-ide-engine
, and also ofHaRe
, but then without cycles.Comments? Other solutions?