Giter Club home page Giter Club logo

Comments (5)

Jim-Lambert-Bose avatar Jim-Lambert-Bose commented on August 17, 2024 1

we fixed this on Feb 22: eb716ce#diff-37aff102a57d3d7b797f152915a6dc16
in release: v2.0.1
try: go get -u github.com/Bose/[email protected]

from go-gin-logrus.

kisinga avatar kisinga commented on August 17, 2024

It worked
However, I'll leave the issue open since a direct install causes the error

from go-gin-logrus.

Jim-Lambert-Bose avatar Jim-Lambert-Bose commented on August 17, 2024

happy to hear it worked. I need to investigate how to fix this "direct" install issue.

from go-gin-logrus.

Shawn-Silva-Bose avatar Shawn-Silva-Bose commented on August 17, 2024

vgo modules need a bit of extra work when jumping to a major version > 1.

When developers reach v2, semantic import versioning means that a /v2/ is added to the import path at the end of the module root prefix: my/thing/v2/sub/pkg. There are good reasons for this convention, as described in the earlier post, but it is still a departure from existing tools. Realizing this, vgo will not use any v2 or later tag in a source code repository without first checking that it has a go.mod with a module path declaration ending in that major version (for example, module "my/thing/v2"). Vgo uses that declaration as evidence that the author is using semantic import versioning to name packages within that module. This is especially important for multi-package modules, since the import paths within the module must contain the /v2/ element to avoid referring back to the v1 module.

We expect that most developers will prefer to follow the usual “major branch” convention, in which different major versions live in different branches.

vgo-modules

I think the options are:

  1. Make branches for each major version with correct go.mod and imports

    • go.mod (module github.com/Bose/go-gin-logrus/v2)
  2. Move v2 to a subdirectory with its own go.mod in master.

  3. Update go.mod on master and release directly from there, possibly introducing issues for downstream users not utilizing go modules yet. (unintentional package updates)

Releasing modules v2 or higher

from go-gin-logrus.

Jim-Lambert-Bose avatar Jim-Lambert-Bose commented on August 17, 2024

Thanks Shawn. I didn’t realize the implications when I rev’d to v2. I’ll make some decisions next week about this and hopefully choose a way fwd that won’t be too painful.

from go-gin-logrus.

Related Issues (4)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.