Remove all the plugins in flutter_quill_extensions

[ellet0]

Most of the plugins break all the time, and because of that, the whole app won't build and run unless we remove the package itself

Every day, I see the app breaks on macOS, Linux, Windows, and more, and most of the time, we can't fix it because it's not from our side

Unless we go there and debug the library, send a pull request and wait sometime until we fix everything, and then it will get fixed

Instead, what we will do is use a callback, and the developer must implement it either with custom code or using a prebuilt plugin

We don't have to remove all the plugins, just the ones that are not from the flutter community and flutter team

[singerdmx]

what will be the replacement if you remove the plugins?

[ellet0]

what will be the replacement if you remove the plugins?

For example, saving images to the gallery with album, the extensions package will require impl for saving the images to the gallery and in the documentation, and by default, we will recommend gal, and so on

We will avoid building failures, and that is what is important

We don't want the whole app to break just because certain plugins don't work. This way, the developer can replace the plugin very easily

[singerdmx]

If you want to copy over the code, you can always do that when it breaks when you have to fix it

[singerdmx]

Don't force users to implement things please
Always provide default and provide choice for them to customize

[singerdmx]

How come it will break if we are using a specific version of lib? Weird

[ellet0]

How come it will break if we are using a specific version of lib? Weird

For every version, we have to test it on all the 6 platforms and see if it works fine

And if we don't update, it will not support the latest api of Android, iOS, and flutter, etc..

The developer might already use the latest major version of the plugin in his project, and it will conflict and fail to get dependencies

Besides, sometimes the plugins just don't work, and I don't know how to get the issue

I saw a lot of reports, and even outside of the issues in this repository

For some people it will work and for some it won't and you can't find out the reason easily

And what if the developer doesn't want any package that contains any plugins for some reasons?? He/she can override the implementation but can't remove the plugin

[singerdmx]

Ok the issue is when we upgrade. Make sense

Just make sure user can easily use it then

[ellet0]

Ok the issue is when we upgrade. Make sense

Just make sure user can easily use it then

The example needs to be remaked, at least in my opinion

I will cover how to sync the images, files with firebase, etc...

And more

And it will will still be based on the current example

But currently I'm refactoring the flutter quill extensions

[singerdmx]

Sounds good

[singerdmx]

Make the user experience that they can try it out without minimum efforts first

[singerdmx]

and the developer must implement it either with custom code or using a prebuilt plugin

This is what I am against