chore(deps): improve dependencies constraints for compatibility #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The versions listed in
pubspec.yaml
indicate the minimum required for dependenciesand do not affect those used in the client's application.
For more information, visit:
The
pubspec.lock
should be included only for application packages, which contain the used dependencies versions.When the client runs
flutter pub get
they will get the latest compatible dependencies at the time until they runflutter pub upgrade
. Theflutter pub upgrade --major-versions
updates the major versions inpubspec.yaml
.Changes
Aditional Context
There is an analysis warning coming from
unintended_html_in_doc_comment
which will be enabled by default and part of the core set starting from5.1.0
. I ignored the warning to avoid additional changes.This repo will probably need an
example
so contributors and CI can test against the latest dependencies (pubspec.lock
included).This PR fixes an issue on the Flutter Quill repo:
Details