Proposal: Register upload handlers in config

[nerg4l]

It would be great if the handler registration would be in the config file intead in the HandlerFactory. So handlers could work similarly to providers. This would make the library more extendable.

• Ability to remove unused handlers
• Developers could extend the library easyer (without the need of implementing the whole library)

What do you think about this?

[pionl]

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' => []
]

[nerg4l]

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.

[pionl]

Working on it

[pionl]

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).