Slack Dropzone Plugin about lexical

[acywatson]

One approach is to extract the Dropzone functionality from the editor but ideally it is part of the editor state since the shared state simplifies managing the attached files.

I would advise you to do this outside of the editor if you don't care about the position of this attachment within a document. The tradeoffs of trying to shoehorn this into the editor state model are just not worth it (imo) if all you need is to attach some images to the document.

[hazirmagron]

One approach is to extract the Dropzone functionality from the editor but ideally it is part of the editor state since the shared state simplifies managing the attached files.

I would advise you to do this outside of the editor if you don't care about the position of this attachment within a document. The tradeoffs of trying to shoehorn this into the editor state model are just not worth it (imo) if all you need is to attach some images to the document.

I ended up following your advise. I feel like it is a compromise to keep the Dropzone functionality non-integrated since I have to manage the state for file uploads separately from everything else. It works well though so I'm somewhat satisfied.

Here is what I ended up doing for anyone who wants to implement similar functionality:

• A custom DropzonePlugin component that is responsible for: 1) drag / drop event handling; 2) Rendering a DropzoneArea UI; 3) Rendering thumbnail previews of uploaded images.
• Object URLs for selected files are stored in Redux state. This allows me to append files from sources other than the Dropzone (e.g. FileUploadButton in the toolbar).

Would appreciate your feedback on this approach @acywatson - for myself and future readers