Also, I wouldn't add a boolean to enforce only the lowercase.

But a flag with constants (a iota maybe, or string) to control if log message should start with an uppercase letter (as state in the section about error strings in Go convention), a lowercase letter (what you want to do), or simply do not enforce this (that would be the default behavior).

Please read this for the context

• feat: implement -msg-style #76 (comment)

Done, how about this?

I like that it is not a boolean anymore, this can be expanded to regular expressions later on, as long as it does not match with upper or lower constants it can be treated that way.

Also added iPhone to the test cases, hope you like it more! Cheers.

Amended your suggestion without changes (only added two missing curly braces and reformatted). Tests are green, the suggestion was correct well done! :-)

Amended your suggestion without changes (only added two missing curly braces and reformatted). Tests are green, the suggestion was correct well done! :-)

Yeah ! ✌️

Good thing to know, the review and feedbacks I made was done with my phone only. 💪 So I'm pretty amazed it worked directly 😅

Please note, I'm a random Gopher, and compulsive code reviewer. I have huge curiosity about linters. Your PR came to solve issue I'm facing too. That's why I jumped in the PR and made feedbacks because I liked your implementation and I had some feedbacks. I enjoyed you were open to them.

Let's now wait for owner or maintainer feedbacks.

If you liked what I suggested and how I helped you, I would like to suggest you to add a Co-authored-by tag in your commit message.

You can take a look here if you never used it

• https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors#creating-co-authored-commits-on-the-command-line
• refactor: set openapi server url as close to startup as possible go-fuego/fuego#273 (comment)

Also, please note you should consider updating your commit message that only mentions "lowercase" feature you started with. I think you should update it.

Let's now wait for owner or maintainer feedbacks.

I swear I thought it was you... :-D Cheers.

@lzap hey, thanks for the PR (and @ccoVeille for the review), I'll take a look shortly!

Codecov Report

Attention: Patch coverage is 94.44444% with 2 lines in your changes missing coverage. Please review.

Project coverage is 85.14%. Comparing base (a72e66b) to head (1f0d37e).
Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
+ Coverage   84.01%   85.14%   +1.13%     
==========================================
  Files           2        2              
  Lines         269      303      +34     
==========================================
+ Hits          226      258      +32     
- Misses         35       37       +2     
  Partials        8        8              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Don't worry about the failing linter check, that's on me to fix.

I'm thinking about the following renames:

• MsgFormat -> MsgStyle (because we're talking about styleguides in the conversations above)
• upper -> capitalized (because we're only checking the first character)
• lower -> lowercased (technically, we're not checking the whole message to be in the lowercase but we might add such check in the future)

With this, we can easily add new style options in the future, such as dotted to check whether the message ends with a dot (uncommon, but might be useful).

@lzap @ccoVeille hope you guys don't mind.

Otherwise, LGTM.

I just pushed v0.10.0, expected to land in the next golangci-lint release.