-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit Contentlet: Create dropzone component #25782
Comments
The idea behind this component is that we should be able to put it inside areas or zones of any page and allow the user to drop files in it... once the file is dropped we need to emit that file to the parent so it can take care of whatever. I think we need to build this on top of a |
* dev: create dot-drop-zone component * dev: create dot drop zone value accessor directive * dev: allow drop one file * test: setup tests * test: dot-drop-zone component * dev: prevent DragOver behavior to allow drop event * test: fix tests * dev: emit dragStart and DrahStop events * test: add tests for directive * dev: create dotDropZone Value Accesor Story * dev: fix CodeQL warning * dev: fix mimeType Validation * dev: add addon-actions to story-book * feedback: unify allowedExtensions & allowedMimeTypes * feedback: emit error on drop * feedback: rename dot-drop-zone @output * feedback: rename @Ouput fileDrop to fileDropped * dev: add validity object * dev: add NG_VALIDATORS to the DotDropZoneValueAccessorDirective
This is the placeholder for binary field. |
Parent Issue
#25445
Task
We need to develop a component that enables Drag & Drop functionality for file uploads. We can take a look at this
PrimeNg
component to see if we can use it: https://primeng.org/fileuploadProposed Objective
Core Features
Proposed Priority
Priority 3 - Average
Acceptance Criteria
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
#24362
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: