Skip to content

Additional names for units #739

@j0hnm4r5

Description

@j0hnm4r5

This probably belongs more in a discussion area than as an issue, but I don't see one, so here we go!

I'm looking for your thoughts on the best way to handle additional unit names, specifically ones that are underscore separated or camel/Pascal case.

Options

  1. Convert them manually before running them through the convert library. The downside of this is that you lose typesafety since it's happening at runtime. The upside is that the library remains opinionated.
  2. Update the codebase with new names for every unit. The downsides are added codebase complexity and maintainability is decreased (especially if there's ever a need to add more names in the future). The upside is there's no major modifications to how the library works.
  3. Convert them within convert. Similar to 1, but a nicer experience for any library users.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions