flutter-error-code-gen

To generate Dart error-code enums, extract error code tables from docs/api/*.md files and map them to descriptive enum members. This produces a reusable Dart enum class under lib/features/{module}/data/error_codes, replacing magic numbers in controllers and keeping code in sync with API contracts.

The best way to prevent magic numbers is to generate a Dart enum class from your API error-code definitions. By extracting codes from docs/api/*.md and mapping them to descriptive enum names, you ensure consistent client-side constants across all Flutter modules.

Yes, you can sync Dart error code enums by reading docs/api/*.md files to extract error code tables. This process maps the codes to descriptive enum members and outputs a {module}_error_codes.dart file, ensuring your client-side constants match the API contract.

Generating Dart enums from markdown requires no external dependencies. It reads your existing docs/api/*.md files to extract error code tables and directly outputs the Dart enum class file into your Flutter project structure without needing additional packages.

When generating error code enums, the tool structures files by outputting to lib/features/{module}/data/error_codes/{module}_error_codes.dart. This creates a {Module}ErrorCodes enum class that organizes client-side constants cleanly within each specific feature module.