Elm Defaults

Core Elm coding conventions and idiomatic patterns

Default

Language / Topic

Elm

Rules

Elm Defaults · balanced balanced

- Use `camelCase` for all values, functions, and record fields; use `PascalCase` for type names, type aliases, and custom type constructors.

- Use the `|>` pipe operator to write data transformations top-to-bottom — avoid nesting function calls more than two levels deep.

- Never use `Debug.log` or `Debug.todo` in production code — remove all debug helpers before committing.

- Annotate top-level function type signatures explicitly — Elm infers them but annotations serve as documentation and surface errors earlier.