Module naming convention question

[valan]

I'm developing few custom module classes derived from WireData and WireArray. They are neither Fieldtype (as do not work with db) nor Inputfield (as not used in rendering). Later they may be used in Fieldtypes and Inputfields.

Is there  "PW way" to name such type of modules?

 

[horst]

If I understand you right, the only convention is to use CamelCaseClassnames and use the same name for the File- & optional Foldername:

site/modules/ValanCustomModule

site/modules/ValanCustomModule/ValanCustomModule.module

The first part is used for grouping modules in the table view of modules list, so you may want to use something meaningful for that part (?)

[teppo]

You've probably seen this already, but this old post from Ryan includes some general tips: 

Like Horst pointed out above, the name doesn't really matter that much, as long as it makes sense to you. That being said, https://martinfowler.com/bliki/TwoHardThings.html