Now, the AWS S3 options for server side encryptions are passed to the
upload handler. Thus, the client can specify the AWS options and use
AWS Server Side Encryption.
Without this change, generated Swagger spec for the upload operation
does not have `container` parameter even it's a variable on the path.
As a result, the sepc fails validations.
An optional `container` is added to the remote method. Conditional
check is added to ensure backward compatibility.
Per Swagger spec 2.0, parameters coming from the path must be marked
as required.
Before this change, the Swagger spec produced by loopback-swagger
was not valid because path parameters were optional.
Note that this commit does not fix the problem of the "uploaded"
method which does not have any swagger-supported parameters now,
and therefore the swagger spec will remain invalid (but with less
errors).
* Fix eslint (Raymond Feng)
* Replicate new issue_template from loopback (Siddhi Pai)
* Fix insert of finalNewLine (Loay)
* Replicate issue_template from loopback repo (Siddhi Pai)
* fix lint (Raymond Camden)
* Support nameConflict and makeUnique options (Raymond Camden)
* Fix#185: Validation failures crash server (Jeff Burn)
* fix scope error (ole3021)
* added file field name into getFilename function (Jose De Gouveia)
* added file field name into getFilename function in storage-handler (Jose De Gouveia)
* Added support for external providers as npm modules. (Cristobal Vergara)
* added maxFieldsSize override to formidable limit (Oscar Bernal)
Fixes issue where upload and download methods in FileSystemProvider
cause crashes in downstream methods by not returning streams in error
scenarios
- Add streamError, readStreamError, writeStreamError helper function
- Wrap all returns from upload / download methods in streams
- Fix incorrect format string
- Add new unit tests
Now, the AWS S3 options for server side encryptions are passed to the
upload handler. Thus, the client can specify the AWS options and use
AWS Server Side Encryption.
Without this change, generated Swagger spec for the upload operation
does not have `container` parameter even it's a variable on the path.
As a result, the sepc fails validations.
An optional `container` is added to the remote method. Conditional
check is added to ensure backward compatibility.
Per Swagger spec 2.0, parameters coming from the path must be marked
as required.
Before this change, the Swagger spec produced by loopback-swagger
was not valid because path parameters were optional.
Note that this commit does not fix the problem of the "uploaded"
method which does not have any swagger-supported parameters now,
and therefore the swagger spec will remain invalid (but with less
errors).
Miguel González Aravena
Diana Lau
Timo Wolf
Rand McKinney
Raymond Feng
Miroslav Bajtoš
Kevin Delisle
Sakib Hasan
Allen Boone
Siddhi Pai
Jose De Gouveia
Jeff Burn
Oscar Bernal
ole3021
Cristobal Vergara
Raymond Feng