You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a new suggestion which is using one version for all the packages from this library (flutter_quill, flutter_quill_extensions, flutter_quill_test, quill_html_converter)
For example when we make a new change to one of the packages we will change the version for all of them
Of course, we will put that in one place to avoid changing it from multiple files
The Advantages:
Consistency, It will become clear which version is compatible with another
we can automate the publishing of all the packages in one place from GitHub releases
The Disadvantages:
Version Bumps for All, we will have to change the version number for all libraries every time we make a change to one of them and we want to release, it doesn't sound like a big deal to us because we publish only when we make too many changes for all the packages and not just single change, or hotfixes but we still want the community vote on this
There might be more
We would like to hear your vote and thoughts about this, thank you for your attention!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have a new suggestion which is using one version for all the packages from this library (
flutter_quill
,flutter_quill_extensions
,flutter_quill_test
,quill_html_converter
)For example when we make a new change to one of the packages we will change the version for all of them
Of course, we will put that in one place to avoid changing it from multiple files
The Advantages:
The Disadvantages:
We would like to hear your vote and thoughts about this, thank you for your attention!
8 votes ·
Beta Was this translation helpful? Give feedback.
All reactions