[MGNLUI-6139] Should inform developer when an invalid field is used on a Vaadin declarative layout for a form Created: 17/Jun/19 Updated: 10/Mar/21 |
|
| Status: | Accepted |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Epic Link: | Declarative layout |
| Description |
|
When a developer places a field on a vaadin declarative layout which is used for a form, but the property is not defined on the form: This is currently implemented, but should be removed: 2. The system should inform the developer that the field is invalid.How best to do this needs some discussion on technical feasability. |