docs: track Rust Bazel target follow-up
This commit is contained in:
@@ -102,6 +102,9 @@
|
||||
- better remote deployment
|
||||
- expose remote deployment as a flake app, replacing the Fish-only `deploy-to` workflow
|
||||
- centralize shared system group names, starting with the `storage` group
|
||||
- Investigate Rust Bazel target structure.
|
||||
Prefer clear per-file dependency edges, but `rust_library` maps each target to a crate.
|
||||
Decide whether wrapper rules or another pattern can improve graph clarity without forcing artificial crate boundaries.
|
||||
|
||||
## nix refactor
|
||||
|
||||
|
||||
Reference in New Issue
Block a user