Fix the build problem of wash-lib with --no-default-features flag.

[rimbi]

Feature or Problem

Fixes the build problem of wash-lib with --no-default-features flag.

Related Issues

Fixes issue #862

Release Information

N/A

Consumer Impact

N/A

Testing

build succeeds in crates/wash-lib: cargo build --no-default-features

Unit Test(s)

N/A

Acceptance or Integration

N/A

Manual Verification

N/A

[brooksmtownsend]

Thanks for filing this @rimbi ! I just had a few requests to see if we needed to gate as many modules behind the NATS feature flag. Let me know if my assumption is incorrect.

Otherwise, my only other request is to update the module documentation at the top of lib.rs to detail the new modules that are behind the nats feature flag. Looking forward to it!

[rimbi]

Thanks for filing this @rimbi ! I just had a few requests to see if we needed to gate as many modules behind the NATS feature flag. Let me know if my assumption is incorrect.

Otherwise, my only other request is to update the module documentation at the top of lib.rs to detail the new modules that are behind the nats feature flag. Looking forward to it!

Hi @brooksmtownsend . What do you mean with to detail exactly? Listing them in the doc? It may cause a duplication.

[brooksmtownsend]

Hey @rimbi all I mean is at the top of wash-lib's src/lib.rs there's this comment:

//! | Feature Name | Default Enabled | Description |
//! | --- | --- | --- |
//! | start | true | Contains the [start](start) module, with utilities to start wasmCloud runtimes, NATS, and wadm |
//! | parser | true | Contains the [parser](parser) module, with utilities to parse `wasmcloud.toml` files |
//! | cli | false | Contains the build, cli, and generate modules with additional trait derives for usage in building CLI applications |
//! | nats| true| Contains the [app](app) module with a dependency on `async_nats` |

I just wanted to add the other modules to the list by the nats flag along with app to match the list of modules there. Does that make sense

[rimbi]

Hey @rimbi all I mean is at the top of wash-lib's src/lib.rs there's this comment:

//! | Feature Name | Default Enabled | Description |
//! | --- | --- | --- |
//! | start | true | Contains the [start](start) module, with utilities to start wasmCloud runtimes, NATS, and wadm |
//! | parser | true | Contains the [parser](parser) module, with utilities to parse `wasmcloud.toml` files |
//! | cli | false | Contains the build, cli, and generate modules with additional trait derives for usage in building CLI applications |
//! | nats| true| Contains the [app](app) module with a dependency on `async_nats` |

I just wanted to add the other modules to the list by the nats flag along with app to match the list of modules there. Does that make sense

done! 👍

[rimbi]

@brooksmtownsend is the failing test a glitch, or?