Guardrails and audits for custom casing of property names
k
klara@avo.sh
Currently Avo allows for standard casing conventions to be enforced when naming event and properties, and custom casing conventions for events.
Some teams do however have custom casing for property names, for example snake_case with two underscores differentiating between parts of a sentence.
Jessica DeLuca
Perhaps this is a separate guardrail feature request - we'd like to programmatically stop properties which have a whitespace in the name from being created (ie- do not allow whitespace in property name).
k
klara@avo.sh
Merged in a post:
Custom casing for event and property name enforcement
Thora Gudfinnsdottir
Currently Avo allows for standard casing conventions to be enforced when naming event and properties.
Some teams do however have custom casing, for example snake_case with two underscores differentiating between parts of a sentence.
J
Jake Schlack
Our team needs this too. We have events that refer to product names that have custom casing (i.e. products that are in all caps, products that start with a single lowercase character) which gets flagged by inspector as not being in capital casing. It would be wonderful to be able to custom configure inspector so that these could be entered as legitimate and preferred casing.