The cargo-workspace from maikklein

cargo-workspace's People

Contributors

Stargazers

Watchers

cargo-workspace's Issues

Support non-explicit workspace children

Looking at the code, it looks like the assumption is that the workspace table in the root Cargo.toml has content. In case of my repo, there's no content there and all children packages are auto-detected because of the relative (child) paths under dependencies table.

$ cargo workspace --help
thread 'main' panicked at 'Is not a workspace: Error { inner: ErrorInner { kind: Custom, line: None, col: 0, message: "missing field `members`", key: ["workspace"] } }', src/libcore/result.rs:860
stack backtrace:
   0:        0x101ce2d03 - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::hfebda55a0148f0d8
   1:        0x101ce62ef - std::panicking::default_hook::{{closure}}::h42d7518fb451881e
   2:        0x101ce5f6b - std::panicking::default_hook::h187f0cce2cdf6403
   3:        0x101ce84ca - std::panicking::rust_panic_with_hook::hcc9e45ce1503358a
   4:        0x101ce8364 - std::panicking::begin_panic::h64dd529720e55854
   5:        0x101ce82e2 - std::panicking::begin_panic_fmt::h3c31ecee09d7435b
   6:        0x101ce8247 - rust_begin_unwind
   7:        0x101d0d4d0 - core::panicking::panic_fmt::hd9dc6c4915cbf1ab
   8:        0x101cba40b - core::result::unwrap_failed::hbb534b697d8c2d1a
   9:        0x101cc2765 - cargo_workspace::main::h2e598dc10dbee162
  10:        0x101ce92dc - __rust_maybe_catch_panic
  11:        0x101ce87d4 - std::rt::lang_start::hb8c8e7e0d07e53cc

Recommend Projects