Qorus’ Recommended Naming Conventions


Every organization should come up with its own naming conventions; the naming conventions described here are recommendations that can be used as a starting point for new projects.

The format of names has no functional impact on the system; the naming convention should provide consistency and clarity of implementations and configurations across development releases and therefore helps to reduce long-term development and maintenance costs.

Qore NamingĀ Conventions

  • ModuleName
  • function_name
  • methodName
  • variable_name
  • classVariableName, staticClassVariableName

Camel case names should have the first letter of each word or acronym capitalized; ex:

  • HtmlClass
  • DbInterface

Note: for unused variable it is commonly used _ (e.g. int sub foo(int x, auto _) { return x + 1; }

See Qore Naming Conventions in the Qore Programming Language Wiki for more information.

Qorus NamingĀ Conventions

Qorus Objects

  • async-queue-name
  • connection-name
  • event-name
  • fsm-name
  • job-name
  • mapper-name
  • pipepine-name
  • service-name
  • StepName
  • tests: should have the same name as the interface being tested without the version number in the test file name, unless there are multiple versions of the object in Qorus used at the same time (ex: workflows or in some classes classes or mappers)

Library Files

Library files should have the same name as the class defined. Only one library object should be defined in each file unless the library object is a part of the fundamental infrastructure for a project.

Grab your FREE application integrations eBook.
You'll quickly learn how to connect your apps and data into robust processes!