Skip to content

Deprecate Dropzone for 2.x, remove it in 3.x #2748

@Kocal

Description

@Kocal
Member

For the same reasons than #2732, #2733, #2740, ...

Activity

added this to the 3.x milestone on May 19, 2025
smnandre

smnandre commented on May 24, 2025

@smnandre
Member

To me there really is something to offer there, but not with the current version clearly.

So let's start working on the next version? @sblondeau ? :)

changed the title [-]Deprecate DropZone for 2.x, remove it in 3.x[/-] [+]Deprecate Dropzone for 2.x, remove it in 3.x[/+] on May 24, 2025
Kocal

Kocal commented on May 24, 2025

@Kocal
MemberAuthor

What do you have in mind? 👀

Because at the moment, Dropzone is legit only a FileType with an already configured placeholder attr and few opinionated Twig, JS and CSS code.

smnandre

smnandre commented on May 24, 2025

@smnandre
Member

cf #2642 #2704 #2747

And it's a package used.. because a decent image upload preview is something interesting.. But if this is only JS i'm still on the same position there is no added value.

But ... if this comes with other things related to back-end, I do see the point

Kocal

Kocal commented on May 24, 2025

@Kocal
MemberAuthor

As you said in #2704 (comment), I also think providing opinionated Twig/JS/CSS code is not safe enough for us nor the user.

Maybe, instead we can provide some Twig components to let user define their own UI:

<twig:Dropzone>
    <twig:Dropzone:Preview>{# ... #}</twig:Dropzone:Preview>
    <twig:Dropzone:Upload>{# ... #}</twig:Dropzone:Upload>
</twig>

but, that also too opinionated...

When deprecating and removing this package, I had in mind to migrate it in a UX Toolkit kit, through the Recipe system:

  • bin/console ux:toolkit:install-recipe Upload
  • install a dedicated FormType, some Twig templates/components, a Stimulus Controller, and styles
  • the files mentioned above would be fully customizable (since it uses the same behavior than installing a Component from an UX Toolkit kit)

WDYT?

smnandre

smnandre commented on May 24, 2025

@smnandre
Member

Seems a very good idea 🤝

smnandre

smnandre commented on Jun 25, 2025

@smnandre
Member

Well i'm having more and more doubts

https://packagist.org/packages/symfony/ux-dropzone/stats

I still agree with your idea but we'll see end of summer how it goes

Kocal

Kocal commented on Jun 25, 2025

@Kocal
MemberAuthor

I feel like we should not deprecate it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @smnandre@Kocal

        Issue actions

          Deprecate Dropzone for 2.x, remove it in 3.x · Issue #2748 · symfony/ux