exported: report differently a method that case was altered

[ccoVeille]

package sandbox

// Foo is OK
func Foo() {}

// FoobarQuux was renamed to FooBarQuux
func FooBarQuux() {}

The classic example of this is a method where an acronym or a Go initialisms was fixed

CheckJson => CheckJSON

revive reports the right things yet, but it could be improved.

But because golangci-lint exclude EXC0012 by default.
This one is not reported via golangci-lint.

We should consider trying to detect it, and report another message that won't be caught by EXC0012

Here the idea is to compare the lowercase name of the method, we can be 100% sure the method was renamed.

Please note #1235 is a special case of #1236

• exported: report differently a method that is now exported #1235
• exported: report differently a method that case was altered #1236

[chavacava]

IMO there is not enough aggregated value to justify the enhancement (but it's only my opinion)

[ccoVeille]

Let's stick with #1235 then, and use a wording that fits both, OK for you?