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
Just to try and fill out how this feature might work, here is one idea:
Add a top level packages field to mono_repo.yaml. Or possibly a new file (mono_repo.packages.yaml?).
This would have the same format as a dependencies section in a pubspec.
The 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.
It would probably fail if a sub-package depends on a package not listed in this global list, and ask you to add it. Or if we got really fancy prompt if you want to add it.
Update the mono_repo validate command to ensure all the pubspecs were up to date (may get this for free?).
The mono_repo pub <command> commands continue to work as they do today, but get consistent versions.
To use with
mono_repo pub get
andmono_repo pub upgrade
.The text was updated successfully, but these errors were encountered: