feature 0.2.0

See which features are enabled and WHY
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

# Features

Check why and how a dependency in your workspace gets enabled. This is useful in cases where you encounter weird build errors which are caused by unintentional inclusion of dependencies or features.

## Install

```bash
cargo install feature
```

## Examples

Using [substrate](https://github.com/paritytech/substrate) as example to find out how `node-cli` depends on `pallet-proxy`:

```bash
feature trace node-cli pallet-proxy
```

output after a few seconds (currently un-optimized :see_no_evil:):

```pre
[INFO  feature] Using manifest "../substrate/Cargo.toml"
[INFO  feature] Calculating shortest path from node-cli to pallet-proxy...
[INFO  feature] The shortest out of 2 paths:
node-cli -> kitchensink-runtime -> pallet-prox
```

## Roadmap

- [ ] Add feature information to the enabled deps
- [ ] Allow manual skipping of dev dependencies (currently always skipped)
- [ ] Introduce filters for versions and features for argument `to`
- [ ] Optimize `shortest_path` function
- [ ] Create lint rules which can be used to validate that certain constraints in the work-space hold