Skip to content

Refactor templates in Everglow.Function #321

Description

@CloudeaSoft

Description

Some old templates suffer from numerous issues, such as poor code style, unused code, flawed design, and insufficient comments. Developers often must copy nearly the entire template and edit it, resulting in significant code duplication.

Expected

  1. Unify file naming, avoid inconsistent casing like ClubProj_metal or ClubProj_Smash_metal. This applies to both classes and other resources.
  2. Standardize naming conventions: use camelCase for fields and PascalCase for properties.
  3. Organize class members by category (e.g., fields together, properties together, methods together).
  4. Rename SetDef() to SetCustomDefaults() for better clarity.
  5. Expose only essential, overridable core methods and provide more custom hooks.
  6. Add documentation and example code for every template.

Progress

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions