document --profile --cargo-profile --config-path

[TriplEight]

cc #267
cc #269

[taiki-e]

We have intentionally not documented nextest-specific options; as the help message states, you can refer to them using cargo nextest run --help.

cargo-llvm-cov/docs/cargo-llvm-cov-nextest.txt

Line 10 in 08015c4

[NEXTEST_OPTIONS] Options for cargo-nextest; For more information try `cargo nextest run --help`

The reasons are the same as those stated in #267 (comment).

This design eliminates the need to respond to each addition or deletion of CLI flags and also makes it easier to maintain compatibility with older cargo-nextest.

Also what you are editing is a help message for subcommands unrelated to nextest.

[TriplEight]

We have intentionally not documented nextest-specific options; as the help message states, you can refer to them using cargo nextest run --help.

Thanks for the clarification, I understand. But there's a certain confusion in cargo native and nextest --profile and --cargo-profile flags. I wanted to address it.

[TriplEight]

Maybe it makes sense to have a "supported nextest flags" category,
as per #267 (comment)

cargo-llvm-cov doesn't parse all the cargo-nextest CLI flags, but only those necessary for cargo-llvm-cov to work properly, and just passthrough everything else to the cargo-nextest.

[taiki-e]

as per #267 (comment)

cargo-llvm-cov doesn't parse all the cargo-nextest CLI flags, but only those necessary for cargo-llvm-cov to work properly, and just passthrough everything else to the cargo-nextest.

What I mentioned there relates to flags that do not work unless the cargo-llvm-cov also recognizes them, and there are in fact many flags that work just fine even if the cargo-llvm-cov does not recognize them.

It would be great if someone could exhaustively test for compatibility with cargo-nextest options, document and issue warnings about options that don't work, but that would require a lot of work.

[taiki-e]

Closing in favor of #271. Thanks anyway for the PR.