Skip to content

ERO Transformation Refactoring Implementation

This document details the refactoring steps executed to update all repository naming conventions to the agnostic ERO (Event Route Optimiser) acronym.

Refactoring Changes

The refactoring was carried out sequentially:

1. API Configuration Updates

  • Modified wrangler.toml: Updated the worker app deployment name to "ero-edge".
  • Modified package.json: Updated the node package "name" to "ero-api".

2. Frontend Configuration Updates

  • Modified package.json: Updated the frontend package "name" to "ero-app".

3. Master Documentation Updates

  • Updated README.md:
    • Changed the top title to # ERO (Event Route Optimiser).
    • Updated repository clone url and folder directories in instructions to ero.

4. Local Settings Variables