TypeNameCheck

Argh - this one is going to be painful for me. Looks like the type name check enforces a pattern '^[A-Z][a-zA-Z0-9]*$'.

Is there any chance we can get an underscore or dash included with that?

The reasoning - for sony products, their API differs depending on the API's version. Example: setPowerStatus v1.0 has a parameter of boolean and the getPowerStatus v1.0 returns a boolean. However, setPowerStatus v1.2 has a parameter of string and the getPowerStatus v1.2 returns a string.

To handle this in a reasonable manner - I have a "PowerStatus_1_0" class and a "PowerStatus_1_2" class.

That's one example out of about 50 classes named this way (I have one class that has 5 different variations depending on the version).

With out an underscore (or dash) - I'd have to renamed stuff to "PowerStatusOneZero" and "PowerStatusOneTwo" or something screwy like that. Using namespaces to differentiate will also be an even bigger issue (alot of overlap between versions so naming something like 'v1-5.xxx" would be hard to understand when the api would be spread over different namespaces).

Start by locating the TypeNameCheck implementation and any tests covering the current type-name pattern. Review how names are validated, then define tests for the requested underscore or dash variants and confirm that existing valid names remain accepted. Done means the reported versioned class names are handled by the check.