Skip to content

Refactor service object variable names to camelCase #45

Description

@markgoho

Background

Currently, many service object variable names use descriptive names like memberAdminService, newsletterService, etc. We should standardize these to use consistent camelCase naming throughout the codebase.

Scope

  • Backend services in /functions/src/
  • Frontend services in /members/src/app/services/
  • Update all variable declarations, parameters, and references

Examples

// Current
const memberAdminService = ...
const newsletterService = ...

// After refactor (if needed for consistency)
// Review actual usage and determine best naming convention

Acceptance Criteria

  • All service object variables use consistent camelCase naming
  • No breaking changes to service functionality
  • All tests still pass
  • Code follows project style guidelines

Priority

Low - This is a refactoring task for code consistency, not a functional bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions