Small v2 package annoyance about clover HOT 10 OPEN

Awh found it.
Basically you can't pull from a branch that looks like a version.

golang/go@21f5484

Note that branches with names that overlap with other module query syntax cannot be selected explicitly. For example, the suffix @v2 means the latest version starting with v2, not the branch named v2.

from clover.

thank you very much. I just found a model replace could solve the problem, but it is a ugly solution. ( I had to manual copy your repository.

After you update, it seems perfect to use the normal method. It works. Thanks !!!

from clover.

I could try to delete the tag and create it again

from clover.

Hey, not sure that will solve anything.
Were you able to replicate this by any chance? Might just be something on my setup.

from clover.

go get github.com/ostafen/clover/v2 correctly fetches the last tagged version (which is v2.0.0-alpha.2) on my machine.
That version has not the document package, so what you are getting is correct.

from clover.

That is correct, but usually you should be able to get the latest version by doing go get github.com/ostafen/clover/v2@main to pull from a specific branch. That works fine for branches like v2-store-merge but doesn't work for the v2 branch for some reason, I assume it might have something to do with the way go mod makes assumptions about versions.

from clover.

The version problem is really annoying. Git using v2.0.0-alpha.2, but it is not the latest repository.

The document said the default engine is bblot, but the fact is not, The default engine is /badger/v3. In the v2, I could not found how to switch to the bbolt engine.

The project is good, but the version and doc seems stop the new user.

from clover.

I could not find the way to use the latest repository code. Is there any suggestion?

from clover.

@joyhope: just pushed a new tag, which should fix your issue. Let me know if that works

from clover.

@ostafen so here v2 just meant a 'dev' version (or actually a branch and/but it is 'default' branch)?
the new coming commits all would merged to v2 only, right?
// would you switch to use 'main' as default branch later?

from clover.