feat: partially revert #1387 #1577
Conversation
|
👋 Thanks for contributing to Viper! You are awesome! 🎉 A maintainer will take a look at your pull request shortly. 👀 In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues. ⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9 📣 If you've already given us your feedback, you can still help by spreading the news, https://twitter.com/sagikazarmark/status/1306904078967074816 Thank you! ❤️ |
sagikazarmark
added
the
release-note/new-feature
1387 introduced a rather serious breaking change that's causing pain throughout the community. Even though it fixed a buggy behavior the previous one was still useful to a lot of people. This change introduces a way to revert back to that old behavior. Signed-off-by: Mark Sagi-Kazar <[email protected]>
sagikazarmark
force-pushed
the
partial-revert-1387
branch
from
cf14683
to
4080010
Compare
|
@ldez @jerome-laforge @b-repo @deynekas Is this something you could work with to get back the previous behavior? |
|
Hello, the build tag is a not real solution for us because golangci-lint can be installed with |
1387 introduced a rather serious breaking change that's causing pain throughout the community. Even though it fixed a buggy behavior the previous one was still useful to a lot of people.
This change introduces a way to revert back to that old behavior by adding a build flag
viper_1387.Fixes #1576