Comments (1)
2. doesn't necessarily mean that at that revision all the other packages in the repo are compatible with
build_runner_core
@ that revision -> I drew the conclusion that the in the repo packages have their own life/release-cycle
Correct, although most of the time packages within that repo are cross compatible because we have integration test that use path dependencies on all of them to run tests.
how you handle development. Hypothetical scenario (that kind of happened to me with
package:build
) is that I would like 1 package at a specific revision (tag) and have all the other packages at such a state that works well with that specific revision (eg. based on pubspec.lock file).
Yeah it's common to make a quick local edit to a pubspec.yaml
to flip between path and hosted dependencies and then running a pub get
to resolve things.
We've left this entirely up to manual processes and it has generally worked out OK for us. @jakemac53 or @kevmoo might have different opinions on that part.
I was thinking on having multiple working copies and do sparse checkouts for package directories. That way the repository could remain a mono repo while locally I can handle different revisions/package version independently from each-other.
I only ever make full working copies - I don't bother with partial copies. Often I won't bother with a pub get
in most of the package directories, but it's still an entirely manual process and I sometimes need to double check that I've done a pub resolve since the last time I change deps.
from mono_repo.dart.
Related Issues (20)
- "dart.bat" file not found (anymore) HOT 3
- Generate .github/dependabot.yaml HOT 1
- Flutter Support in Github Actions HOT 8
- Pin hashes for dependencies HOT 14
- Found 1 file excluded from sound null safety
- Allow integration with melos HOT 7
- Flutter package determination HOT 4
- The save-state command is deprecated and will be disabled soon HOT 3
- Option to generate workflow files for automated publishing HOT 1
- add support for dart format
- execution stats for all modules
- option to declare mono_repo support in pubspec.yaml
- add a mono_repo.yaml option to not generate the self-check HOT 4
- Add `concurrency` option for Github actions HOT 1
- update mono_repo so that it can work with dependabot HOT 3
- Support only running jobs for affected packages HOT 3
- Add a way to specify dependency versions for all packages in mono_repo.yaml. HOT 3
- Add a `fix` command to run `dart fix` across all packages HOT 2
- Support wildcard (`major.minor`) SDK version specifiers
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mono_repo.dart.