Flutter
Possible, with the weakest built-in guard. A context is three packages in one folder: contract, src and tests. The API layer is screens and controllers.
The files
Explorer
- pubspec.yamlworkspace, found by pattern
- gen.dart
- boundaries.dartthe guard
- pubspec.yamlgeneratedlists every context, not committed
- main.dart
- contexts.g.dartgenerated
- context.yaml
- pubspec.yaml
- pubspec.yaml
- register.dart
- pubspec.yaml
- policies.yaml
- flags.yaml
What the tools allow
| Question | Answer | Tag |
|---|---|---|
| Tests inside the folder | yes: 22 pass | MEASURED |
| A planted failing test | fails | MEASURED |
| A misnamed test file | skipped silently; our checker catches it | MEASURED |
| Tests or docs in the web build | 0 found | MEASURED |
| Hot reload after an edit | 0.55 s | MEASURED |
An import the compiler lets through
billing imports orders (real output, shortened)
$flutter analyze
info • The imported package 'orders_ctx' isn't a dependency of the importing package.
$
1 / 2
What changes
| Change | Count | Tag |
|---|---|---|
| Template files moved | 0 of 559 (no features in it) | REASONED |
| alcohol.neon files that change folder | 180 | MEASURED |
| Package files per context | 3 | MEASURED |
| alcohol.neon merge conflicts in 90 real merges | 0 | MEASURED |
What does not work cleanly
- Two generated files are not committed. If they are stale, every Flutter command fails until
task gen. MEASURED - An undeclared import compiles and its tests pass. MEASURED
- Tests on a device were not run. NOT TESTED