Add schema modeling guidance for enum values as lower_snake_case by jack-berg · Pull Request #445 · open-telemetry/opentelemetry-configuration (original) (raw)

Realized we don't consistently model enum value types when reviewing this spec PR.

Ideally, we would have case insensitive enums, but JSON schema doesn't support those without resorting to using regex patterns.

Choosing snake case because we already have modeling guidance saying that property names are snake case.