Open ykmnkmi opened 1 year ago
Just to try and fill out how this feature might work, here is one idea:
packages
field to mono_repo.yaml
. Or possibly a new file (mono_repo.packages.yaml
?).
dependencies
section in a pubspec.mono_repo generate
command would modify all pubspec.yaml
files in the repo to fill in the version constraint listed in this file for each dependency.
mono_repo validate
command to ensure all the pubspecs were up to date (may get this for free?).mono_repo pub <command>
commands continue to work as they do today, but get consistent versions.Not only dependenies from pub.dev, but also git dependencies with certain commits. Currently, I am doing this manually, and it's not the first time.
I'm not sure where this feature would be most suitable, maybe pub
feature: mono_repo pub upgrade --from-file=../root_pubspec.yaml
.
The process I described above could work fine for git, path, or pub dependencies. It would just blindly copy the value, which could be anything.
To use with
mono_repo pub get
andmono_repo pub upgrade
.