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.
With this PR I propose some minor repo chores that will make the maintenance of the package slightly easier:
pubspec.lock
files from packages. According to the official recommendation,pubspec.lock
files should not be commited unless it is an application. I noticed in the commit history that some contributors struggled with conflicts in these files.// used for testing
comment with the@visibleForTesting
annotation. That will make the analyzer complain if someone accidentally misusesDependencyConfig
factories.dependency_overrides
for forcing packages to use dependencies viapath
. According to the documentationHence such a change removes the need of updating dependencies in
pubspec.yaml
files for local development, keeping the behavior the same for the actual users. More robust approach would be to usemelos
, but for two packages in the repo that might be an overkill.