[MGNLUI-4369] Create FieldType DefinitionValidator to validate against deprecations Created: 19/Feb/18 Updated: 08/Mar/21 Resolved: 08/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Ilgun Ilgun | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Epic Link: | YAML backwards compatibility |
| Description |
|
We need to inform users about deprecated FieldTypes and the way to do it is to create a DefinitionValidator for field types. This validator should be checking if the given field type is currently in use and if it's deprecated, then this problem should be reported to the user via Definitions app |
| Comments |
| Comment by Roman Kovařík [ 20/Apr/18 ] |
|
This should be implemented in dialog and app descriptor validators. |
| Comment by Roman Kovařík [ 08/Mar/21 ] |
|
Closing this as the new framework doesn't use a field type registry and fields definitions can be deprecated on its own. |