Re: [go-nuts] Linter for checking 'MVS' of go module
Thanks a lot, Shulhan. On Wednesday, December 9, 2020 at 1:03:01 PM UTC+8 Shulhan wrote: > > > On Wed, 9 Dec 2020, 11:42 xiangd...@gmail.com, > wrote: > >> Hi all, >> >> I'm wondering if any linter, or is it practical to make one, checks >> whether a go module's code change conforms the minimal version selection >> rules, say linter warns a v2 is needed if incompatible changes to APIs are >> introduced in the current change under linting? >> > > There is an experiment on tooling called gorelease [1]. I believe its in > working-in-progress [2]. > > [1] golang.org/x/exp/cmd/gorelease > [2] https://github.com/golang/go/issues/26420 > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/25a1ca42-c910-45f4-91d7-14f6866e6538n%40googlegroups.com.
Re: [go-nuts] Linter for checking 'MVS' of go module
On Wed, 9 Dec 2020, 11:42 xiangdong...@gmail.com, wrote: > Hi all, > > I'm wondering if any linter, or is it practical to make one, checks > whether a go module's code change conforms the minimal version selection > rules, say linter warns a v2 is needed if incompatible changes to APIs are > introduced in the current change under linting? > There is an experiment on tooling called gorelease [1]. I believe its in working-in-progress [2]. [1] golang.org/x/exp/cmd/gorelease [2] https://github.com/golang/go/issues/26420 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAMh9%2BYDnGGRAixmxiddNkpX1gbHPSB7NAwatDKP5qCg6z48aJA%40mail.gmail.com.
[go-nuts] Linter for checking 'MVS' of go module
Hi all, I'm wondering if any linter, or is it practical to make one, checks whether a go module's code change conforms the minimal version selection rules, say linter warns a v2 is needed if incompatible changes to APIs are introduced in the current change under linting? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/a57bad3b-a4bb-4507-ada3-95df46606bf3n%40googlegroups.com.
