Support specifying features manually

[ethowitz]

Currently, we always run cargo check and cargo metadata with the default feature set. There will be cases where people need to pass in a list of features manually. We should support them!

[ethowitz]

This is a bit tricky because if you regularly work in different cargo workspaces, you'll need to pass through different features for each workspace--passing features to cargo metadata that don't exist in the workspace results in an error.

This is where having a per-workspace configuration file a la #23 would come in handy. I think I'll wait to implement this till that's done

[aldanor]

Wonder if there's any further thoughts on this? Use-case is - working in a big monorepo that has lots of crates and working on one of them in particular that has a non-default feature which blocks a huge part of the code.

Normally, rust-analyzer would somehow figure it out by default (does it use all-features?), but with cargo-subspace I have to edit this crate's manifest temporarily to add this feature to default = [..] list which works but is pretty hacky and interferes with git state.

[ethowitz]

@aldanor Hi! It is currently possible to pass --all-features on the command line to have cargo-subspace to activate all the available features for crates in the workspace. You'd use it by updating the workspace.discoverConfig.command options in your rust-analyzer config to include the --all-features flag like so:

(this example is for vscode, so it may need to be adapted for your editor's config file format)

{
  "rust-analyzer.workspace.discoverConfig": {
    "command": [
        "cargo-subspace",
        "discover",
        "--all-features",
        "{arg}"
    ],
    "progressLabel": "cargo-subspace",
    "filesToWatch": [
        "Cargo.toml"
    ]
  },
  "rust-analyzer.check.invocationStrategy": "once",
  "rust-analyzer.check.overrideCommand": [
    "cargo-subspace",
    "check",
    "$saved_file",
    "--",
    "--all-features"
  ]
}

Does this support your use case for the time being?

I do plan to work on #23 soon, at which point it would become possible to pass through individual features on a per-workspace basis