...
Given the simplicity of the data, and no forseen future requirements to maintain it as a seperate entity, we propose to use Approach 2.
Approach 3
Store the user-types available in user-profile configuration.
Pros
- Flexible per installation - one can have different user-types - different display-names
Cons
- Difficult to apply business logic based on user-types.
- Difficult to maintain - if someone changes user-types list, especially remove existing value can become a problem for data-consistency.
API Definition
Code Block | ||||
---|---|---|---|---|
| ||||
Response: 200 OK [ "TEACHER", "OTHER"] |
...