Proposal: merge this repo into the main lnd (incompatible versions). about lndclient HOT 3 CLOSED

Maybe decoupling a bit from the LND module could help a bit? I see that some LND parts are their own modules (clock, queue, etc.)

Yeah I think the main thing that'll help is making lnrpc and the related sub-folders into sub modules. This way we can bump new versions of that periodically which should make the whole dependnacy hell adventure much easier.

from lndclient.

Main reason we have it in its own repo is so we can modify it independently of the lnd repo's release/dev/review cycle.

It's possible to use all 3 in a single repo (we do on some of our backend projects, it just takes a bit of finagling with modules. Check our the branches on this repo, we have one that works in line with 0.14 as an example.

from lndclient.

Hey @Roasbeef! Thanks for the prompt response!

I see the reasoning for having this repo separately. Makes sense!

Maybe decoupling a bit from the LND module could help a bit? I see that some LND parts are their own modules (clock, queue, etc.). Maybe some more things used by lndclient could be extracted into their own modules so that lndclient doesn’t depend on the main LND at all? Now that I’m writing this I see how this probably will not help much and could lead to the same situation 🤦‍♂️

I think I finally managed to combine the right versions. I first imported Loop which made lndclient and LND my indirect dependencies. And apparently Go was able to find the right versions. Then I made them my direct dependencies and it continued to work. 😅

from lndclient.