[MGNLUI-7017] Model content with file/binary properties Created: 18/Jan/22  Updated: 13/Sep/23

Status: Accepted
Project: Magnolia UI
Component/s: framework
Affects Version/s: 6.2.15
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by MGNLUI-5886 2 or more UploadFields cannot be used... Closed
Relates
relates to MGNLUI-6991 Cannot Delete An Asset From a DAM Upl... Closed
relates to MGNLUI-6215 DOC: Restructure uploadField document... Closed
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:
Epic Link: DevX Bucket
Team: DeveloperX

 Description   

As a project developer, I want to model content with file/binary properties so that editors can add images to content entries without leaving the form.

ACs

  • support multiple concurrent fields with arbitrary property names
  • do not require complex configuration or custom code (save action, item resolution strategies)
  • support delivery with facilities to resolve links to those binaries
  • offer a clear content-type property type and/or a clear, non-deprecated field-definition to configure such properties and editing experience
  • resolve confusion about upload-field (deprecated) vs. DAM upload-field (not deprecated, also unintuitively doesn't upload to dam) vs. link fields.
  • be usable in dam workspace without further linking (see SUPPORT-13193)

Technical points

  • $type: uploadField definition has been deprecated since 6.2.4, see Upload field and DAM upload field; caution blocks in both pages advise "not to use" these definitions in certain context, without explaining why.
  • We currently go through interesting gymnastics to cover our internal usage:

    While damUploadField is not deprecated, it is no longer annotated as a field type

    —which doesn’t prevent actual usage, just makes it uglier, see this.

  • we are free to upload to DAM behind the scenes if we feel like, and as long as developer and author experience do not suffer from this.


 Comments   
Comment by Christopher Zimmermann [ 15/Mar/23 ]

Is this a Nucleus topic primarily dmaslanka 

Generated at Mon Feb 12 09:42:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.