Simple custom types
Reusability
Simple custom types should be created only when the type is used at least twice in the model. It should be used also when a change should be reproduced for every element referencing it.
For every other case, anonymous types should be leveraged instead.
Naming conventions
Simple custom types should be named using the following convention: type description + Type (e.g. EmailType).
When an enumeration facet is used on a simple type, the naming convention turns to be: enumeration description + Enum (e.g. GenderEnum).
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!