[MGNLCT-29] Validation for model properties Created: 16/Apr/18 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Story Points: | 8 | ||||||||||||||||
| Description |
|
User story:
Defined in the actual content type definition - validation is not a presentation detail. Acceptance criteria:
|
| Comments |
| Comment by Hieu Nguyen Duc [ 14/Sep/18 ] |
|
There are two kinds of validation: validation on UI & validation before saving data into database. What kind of validation would REST do if it used this model? If REST validated in server, why would we have two codes to handle validation with the same model? i.e app & REST. In that case, what kind of validation of the model could be understood? |
| Comment by Mikaël Geljić [ 20/Sep/18 ] |
|
Exactly hieu.nguyen, UI-specific (soft) validation remains defined in the app descriptor for now (until we address synergies with UI). Data-source level validation is exactly what *this* story is about (we just clarified that, no additional ticket). |