Easy to use Angular2 directives for files upload (demo)
- A recommended way to install ng2-file-upload is through npm package manager using the following command:
npm i ng2-file-upload --save
Alternatively, you can download it in a ZIP file.
-
Currently
ng2-file-upload
contains two directives:ng2-file-select
andng2-file-drop
.ng2-file-select
is used for 'file-input' field of form andng2-file-drop
is used for area that will be used for dropping of file or files. -
More information regarding using of ng2-file-upload is located in demo and demo sources.
uploader
- (FileUploader
) - uploader object. See using in demo
onFileSelected
- fires when files are selected and added to the uploader queue
uploader
- (FileUploader
) - uploader object. See using in demo
Parameters supported by this object:
url
- URL of File Uploader's routeauthToken
- Auth token that will be applied as 'Authorization' header during file send.disableMultipart
- If 'true', disable using a multipart form for file upload and instead stream the file. Some APIs (e.g. Amazon S3) may expect the file to be streamed rather than sent via a form. Defaults to false.itemAlias
- item alias (form name redefenition)formatDataFunction
- Function to modify the request body. 'DisableMultipart' must be 'true' for this function to be called.formatDataFunctionIsAsync
- Informs if the function sent in 'formatDataFunction' is asynchronous. Defaults to false.parametersBeforeFiles
- States if additional parameters should be appended before or after the file. Defaults to false.
fileOver
- it fires during 'over' and 'out' events for Drop Area; returnsboolean
:true
if file is over Drop Area,false
in case of out. See using in ts demo and html demoonFileDrop
- it fires after a file has been dropped on a Drop Area; you can pass in$event
to get the list of files that were dropped. i.e.(onFileDrop)="dropped($event)"
Please follow this guidelines when reporting bugs and feature requests:
- Use GitHub Issues board to report bugs and feature requests (not our email address)
- Please always write steps to reproduce the error. That way we can focus on fixing the bug, not scratching our heads trying to reproduce it.
Thanks for understanding!
The MIT License (see the LICENSE file for the full text)