[MGNLCAT-151] CategorizationTemplatingFunctions.getCategories also works for non-multivalue properties Created: 12/Feb/15 Updated: 19/Dec/22 Resolved: 19/Dec/22 |
|
| Status: | Closed |
| Project: | Magnolia Categorization Module |
| Component/s: | None |
| Affects Version/s: | 2.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | quickwin | ||
| 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)
|
||||||||
| Date of First Response: | |||||||||
| Team: | |||||||||
| Description |
|
Currently getCategories function expects that the property that links to categories is a multivalue property. However a developer may want to configure a dialog such that a content item can only link to one category. getCategories should be flexible enough to handle both situations. |
| Comments |
| Comment by Philip Mundt [ 18/Feb/15 ] |
|
When using the categorization module and the provided tabCategorization + CategorizationFunctions this is considered a non-issue. |
| Comment by Laura Delnevo [ 19/Dec/22 ] |
|
Hello, This ticket is now marked as closed due to one of the following reasons:
If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. Thank you, The Magnolia Team |