singerdmx
Breaking changes of version 11.0.0
This issue will document the breaking changes that are planned for 11.0.0
This issue will be updated as we plan. All breaking changes should be planned here instead of discussing them in different issues.
I propose that we should and need to refactor files that contain several classes that are only used internally.
If you want to see what the problem is with this you can take a look at: editor, text_line, text_block, proxy, default_styles, etc. There are many files of this style that we can perfectly divide into different files (making this avoid creating files with more than 1000 lines that are not always easy to debug)
Update: I have started working on release/v11, if anything is missing, something that shouldn't be done, improvements or an issue, or suggestions for some breaking changes, I'm open for all suggestions.
This major release aims to address issues requiring breaking changes, along with cleanup and refactoring for better organization. See the issue details.
Would you be planning for tables in v11?
For now, we don't have any plans to, we have deprecated it in #2254, and has been removed in v11 (#2338) (not published as stable yet). We might create a highly experimental package (in a separate repo) with this feature though with the current state it's not production-ready.
Reason: We're trying to prioritize existing issues before adding more features to provide more on the surface for more issues and we have agreed on that for now.
@CatHood0
Since the table feature has been removed in the branch release/v11 (#2338), we can create a new package (quill_table_embed or a different name) and publish it as highly experimental in a separate repo. I don't plan to work on it for now though you don't have either, you can only take existing table code from flutter_quill_extensions that was introduced in #1960 so users can use it if they still want to depend on it after 11.0.0. You can create it in FlutterQuill/quill-table or outside of flutter-quill.
It's a minor issue though it requires minimal time too. I can also do it if you prefer.
Since the table feature has been removed in the branch release/v11 (https://github.com/singerdmx/flutter-quill/pull/2338), we can create a new package (quill_table_embed or a different name) and publish it as highly experimental in a separate repo. I don't plan to work on it for now though you don't have either, you can only take existing table code from flutter_quill_extensions that was introduced in https://github.com/singerdmx/flutter-quill/pull/1960 so users can use it if they still want to depend on it after 11.0.0. You can create it in FlutterQuill/quill-table or outside of flutter-quill.
It's a minor issue though it requires minimal time too. I can also do it if you prefer.
I will take care of creating that table, however it will take some time to avoid the same errors that the previous implementation had. Thanks for the suggestion to add the table as a separate package.