Hi,
I have a case where we developing inside a monorepo project where we
distribute shared libs locally (without publishing) and we're using
*replace* directive inside *go.mod*. What we fear is someone changes the
shared libs logic, it might break other applications that use it because we
can'
> On 6 May 2020, at 11.11, Reyhan Sofian Haqqi wrote:
>
> Hi,
>
> I have a case where we developing inside a monorepo project where we
> distribute shared libs locally (without publishing) and we're using replace
> directive inside go.mod. What we fear is someone changes the shared libs
>
>
> The question is why you can't have any version inside the shared libs? How
> do you shared the libs locally?
Because we use monorepo. Maybe git tag works since it's also pointing to a
commit hash? but does it works if we use `replace` directive on go.mod file?
If the replace directive us
> On 8 May 2020, at 14.26, Reyhan Sofian Haqqi wrote:
>
> The question is why you can't have any version inside the shared libs? How do
> you shared the libs locally?
>
> Because we use monorepo. Maybe git tag works since it's also pointing to a
> commit hash? but does it works if we use `
Thanks for your advice! I will try your suggestion right away. I found that
your approach some kind of similar to https://github.com/rogpeppe/gohack.
But it seems we can't use that library since we have our internal tool to
handle the importing of our shared libs. Thanks!
On Friday, May 8, 2020
