Apex: class naming conventions [closed]

Question

I've been coding Apex alone but now other developers will be involved so I am thinking about class naming conventions. This is what I was using:

Class: ClassName

Test class: ClassNameTest

Controller: ClassNameController

Controller test class: ClassNameControllerTest

Web service class: ClassNameService

Web service test class: ClassNameServiceTest

1. Is it good/bad?

2. What is the convention for utility class that contains static methods?

3. Should I add "Trigger" at the and of trigger class name? Some people suggest doing this but triggers are in a separate package with ".trigger" at the end so I find it not needed. Am I wrong?

4. What whould be the naming convention for the instance class which object exists inside controller class?

Answer 1

Check this question What is a good set of naming conventions to use when developing on the Force.com platform? and Apex-Code-Convention on GitHub

As for me, I prefer convention on GitHub.

Answer 2

There is no good/bad when it comes to conventions.

I have seen a lot of code and can assure you that people/organizations have their own naming conventions.

Here is what I do normally:

1. Triggers: tgrTRIGGERNAME
2. Classes: clsCLASSNAME
3. VF Pages: vfpPAGENAME
4. Controllers: vfcPAGENAME
5. TestClasses: testCLASSNAME
6. Utility classes: utilCLASSNAME
7. Classes which handle trigger code: tgrCLASSNAMEHandler