Skip to content

Define and document naming conventions and rename misaligned classes #2091

@kaltokri

Description

@kaltokri

Some examples:

  • Fsm / Atis / Fox vs. AWACS / CSAR / CTLD. AI.AI_A2A_Gci vs. AI.AI_A2G_BAI. -> I suggest upper case for all acronyms.
  • Why Ops.OpsGroup / Ops.OpsTransport / Ops.OpsZone instead Ops.Group / Ops.Transport / Ops.Zone ?
  • Core.MarkerOps_Base -> Core.MarkerOpsBase ?
  • Ops/Intelligence.lua is class Ops.Intel. Rename file to Ops/Intel.lua
  • Ops.Airwing = Ops.AirWing.lua

ToDos:

  • We need to define a naming convention.
  • It must be documented
  • Check which parts are misaligned to the naming convention
  • Check if we can change the misaligned parts without breaking downwards compatibility
  • If a chenage will break downwards compatibility, we need to decide: Do it / don't do it / do it only in development branch

Metadata

Metadata

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions