[MGNLUI-6859] Improve thumbnailView to work with damLinkField Created: 03/Sep/21 Updated: 03/Sep/21 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Normal |
| Reporter: | Leah Staniorski | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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)
|
| Description |
|
The use case is to be able to add the thumbnailView onto a content app with it's source being a damLInkField.
Currently, the thumbnailView only seems to work with the (deprecated) upload field. The only example I could find was the contacts app. When I look at how a contact is stored inside the JCR (see screenshot attached), there is a photo node and thumbnail node. The contacts app detail sub app uses the upload field, so it seems you must use this upload field (which is deprecated) or have this sort of photo node format in order for the thumbnailView to work (with the preview: photo set for the data source as well). Ideally, it would be possible to use just a damLinkField which just stores the dam asset uuid.
|