[MGNLDAM-822] Asset detail editor - validation for binary file must be on par with M-5-UI Created: 03/Feb/20  Updated: 09/Mar/20  Resolved: 09/Mar/20

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 3.0
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Rishab Dhar
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File M5-UI_delete-asset-validation.png     PNG File M6-UI_delete-asset-validation.png    
Issue Links:
Relates
relates to MGNLUI-5656 Improve Upload Field implementation 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: M6 UI & UX Improvements

 Description   

The validation for an empty binary file (on the upload field) on the assets detail subapp should be similar as it is on M.-5-UI (old app).


Case 1: Editing an existing asset - removing its binary file

To reproduce the issue, you must edit an existing item, removing its binary file with the "remove" button (the trash bin button).

Quoting avongunten (from slack)

 the default behavior for field validation is

  • field border turns red (1px)
  • bubble below field shows message

..


Case 2: Adding a new asset without providing the binary file

In this case there is only a red star *.
But there also should be the bubble with the text "This field is required" ... or something similar.

 

 



 Comments   
Comment by Simon Lutz [ 13/Feb/20 ]

Check if any visual issues remain after implementation of linked ticket.

Generated at Mon Feb 12 05:03:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.