RFC: Rename OrmIdentifier to ORMIdentifier and proposed JwtAuthenticator to JWTAuthenticator about authentication HOT 4 CLOSED

I would rather stick with the normal CamelCase naming convention (JwtAuthenticator, OrmIdentifier) we use so far for all core classes and all ecosystem tools, including the core plugins Acl and CO.
True, the ORM namespace is a small expection, but it is also just a namespace.
The rest, especially 100% of all classes are following the convention, though, including:

• AclComponent (ACL)
• CrudAuthorize (CRUD)
• JsonView
• HtmlHelper
• Js and Css stuff in AssetCompress
• CsvView, RssView, ...

Starting sth different now is a small flake naming in the middle of an otherwise quite consistent naming scheme IMO.

from authentication.

I agree with @ADmad argumentation but I also agree with @dereuromark. Either we have them all changed or we stick to the current pattern. We could consider changing this in CakePHP 4.

from authentication.

I think we should not get into the hell of deciding if something is an abbreviation or if not, and how the abbreviation is cased.

While the PHP docs use for example XMLFoo, Symfony and CakePHP use XmlFoo: http://symfony.com/doc/current/components/serializer.html
http://php.net/manual/de/book.simplexml.php

from authentication.

Closing, it's no biggie.

from authentication.