Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix --manifest-path to point to Cargo.toml instead of a directory #20

Merged
merged 1 commit into from
Mar 29, 2022

Commits on Mar 29, 2022

  1. Fix --manifest-path to point to Cargo.toml instead of a directory

    Currently `cargo-subcommand` expects this argument to be a path to the
    directory containing project(s), whereas it should actually point to a
    file specifically named `Cargo.toml`.
    
    Note that this path doesn't appear to be very strict in `cargo`: even if
    pointing to a manifest file within a workspace, packages in the
    surrounding workspace are still built, and are reachable through `-p`.
    
    However, there's a strict requirement on the specified manifest to be
    part of the workspace, which is not enforced in `cargo-subcommand` yet.
    MarijnS95 committed Mar 29, 2022
    Configuration menu
    Copy the full SHA
    5a200dc View commit details
    Browse the repository at this point in the history