You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to this version, I noticed that when there are "." in a key in the config, the config is parsing incorrectly. This provides a bad experience as something like github.com/foo/bar will fail to parse. This was recently corrected in an unreleased PR in viper spf13/viper#673 that I believe will fix this issue when it is released.
I plan to make a PR to fix this as soon as a new release of viper is cut so that this bug will be fixed.
The text was updated successfully, but these errors were encountered:
codyleyhan
changed the title
Keys with dots in them are parsed incorrectly
Config keys with dots in them are parsed incorrectly
Sep 14, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
golangci-lint: v1.18.0
I made a merged PR that added the ability to have users provide error messages for depguard, I had made and tested a similar PR for depguard, but did not do the same checks in this repo. I made a trivial use case of
log
in the test at https://github.com/golangci/golangci-lint/blob/master/test/testdata/depguard.go#L7.After upgrading to this version, I noticed that when there are "." in a key in the config, the config is parsing incorrectly. This provides a bad experience as something like
github.com/foo/bar
will fail to parse. This was recently corrected in an unreleased PR in viper spf13/viper#673 that I believe will fix this issue when it is released.I plan to make a PR to fix this as soon as a new release of viper is cut so that this bug will be fixed.
The text was updated successfully, but these errors were encountered: