[MGNLPN-600] Broken trait definitions should not be visible in trait picker Created: 22/Oct/21 Updated: 26/Aug/22 |
|
| Status: | Open |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | 2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| 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: | AuthorX Maintenance |
| Team: |
| Description |
|
If a trait definition is not valid - for example the $type is not valid, then the definition should 1. Show as a problem in the definitions app. 2. It should not be available in the trait pickers - for example when using "Choose Audience" in the pages app. Notes: If an invalid trait IS used on a component - then even if the trait is fixed later, personalziation is still broken on that content because a class was not correclty added to the voter. |