Proposal: Register upload handlers in config about laravel-chunk-upload HOT 4 CLOSED

Hi,

you already do not need to implement the whole library, you can call Handler:: register(MyOwnImplementation::class), the docs are in Wiki

Anyway, you have a point. It would be easier to provider entry in config. I would not recommend to have in-built handlers in config (updating would be harder), but we could allow user to override the handlers. This should be pretty easy.

... config
'handlers' => [
// A list of handlers/providers that will be appended to existing list of handlers
'custom' => []
// Overrides the list of handlers - use only what you really want
'override' => []
]

from laravel-chunk-upload.

Hello,

You are right. It seems I did not read carefully enough and missed that part. Currently I registered the library as a local repository with composer to be able to add a handler.

You are right about the problems with update process. And this configuration idea looks promissing.

from laravel-chunk-upload.

Working on it

from laravel-chunk-upload.

I've updated the wiki:

• https://github.com/pionl/laravel-chunk-upload/wiki/Controller
• https://github.com/pionl/laravel-chunk-upload/wiki/custom-handler

Integration is updated to use config. Service provider is now partly unit tested (to cover this change).

from laravel-chunk-upload.