Mapping table default values need extra validation
Open
feature
priority: undecided
under discussion
- Dominant language
- Scala
- Stars
- 33
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
## Background
Right now there is no validation applied on the defaults of a mapping table and they can also be inserted multiple times
## Feature
Add validation when creating a default for mapping tables
## Proposed Solution [Optional]
Solution Ideas
1. Do not allow inserting a default for the same field
2. Verify that the type of the default is compatible with the mapping table field type
Contributor guide
Assessment
This issue has not been assessed yet.