Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the casing of github.com/Sirupsen/logrus to match what the project itself uses #380

Merged
merged 1 commit into from
Sep 6, 2018

Conversation

coderanger
Copy link
Contributor

Dep enforces this. I have no idea why it just started bothering me about it but it seemed like a safe thing to fix. Reference https://github.com/sirupsen/logrus/blob/master/example_basic_test.go#L4 or the default name capitalization in github to confirm I'm not off the mark?

@coveralls
Copy link

Coverage Status

Coverage remained the same at 22.778% when pulling c264116 on coderanger:logrus-case into a4224f6 on zalando-incubator:master.

Copy link
Member

@sdudoladov sdudoladov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reference https://github.com/sirupsen/logrus/blob/master/example_basic_test.go#L4 or the default name capitalization in github to confirm I'm not off the mark?

actually both capitalizations work for me but I like uniform things :)

@coderanger
Copy link
Contributor Author

This was apparently a whole big thing back in 2017 sirupsen/logrus#553 (comment) sirupsen/logrus#570 (comment) and I just never noticed until I happened to pull in both postgres-operator and another lib that uses logrus. Apparently lowercase is the Official Solution™ even though it can make your glide cache cranky.

@sdudoladov sdudoladov merged commit 0b75a89 into zalando:master Sep 6, 2018
@coderanger coderanger deleted the logrus-case branch September 6, 2018 08:30
@redbaron
Copy link
Contributor

redbaron commented Jan 9, 2019

this made glide.lock hash incorrect :-/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants