Alex

# Overview The unimplemented message for `IntoJobDefinition` isn't very helpful: ``` no method named `into_job_definition` found for fn item `fn(Context, ...) -> ... {modify_rollup_metadata}` in the current scope the full...

# Overview We currently retain all fetchers when baking the blueprint: https://github.com/tangle-network/blueprint/blob/27bc2432e914177e60576c79d5bb4a2b7803fcc3/cli/src/deploy/tangle.rs#L416-L420 That's an issue for `Testing` fetchers, which will contain a local path. Developers will not want their local...

# Overview When building contracts here: https://github.com/tangle-network/blueprint/blob/105255328a9c1bc0bd84878be7c89415dda81f95/cli/src/deploy/tangle.rs#L289 Multiple things can error: `forge build`, `soldeer update`, missing contracts dir, bad contract name But every error just gets reduced to: ``` Error:...

# Overview In a Tangle job, the following is printed in a loop for every block while waiting for a result: ``` INFO gadget_tangle_testing_utils::node::transactions: Waiting for job completion. Found 0...

There's no (easy) way to get a key without knowing its public key. We should support allowing users to specify a key ID (such as "tangle-default"). ## Unresolved Questions *...

# Overview `cargo tangle gadget create` currently just pulls from the hello world template: https://github.com/tangle-network/blueprint-template It'd be nice to add: - [x] `--repo` and `--path` to specify remote & local...

# Overview In order: - [x] https://github.com/tangle-network/gadget/issues/353 - [ ] https://github.com/tangle-network/gadget/issues/352 - [x] https://github.com/tangle-network/tangle-docs/issues/73

Might be worth allowing the following: * You clone a template, say https://github.com/tangle-network/blueprint-template * You can initialize it in place: `cargo tangle blueprint create --name foo --init` * `cargo-generate.toml` is...

I'd like to use Lofty's parsing utilities in another crate. Just experimenting to see if they're general enough for external use.

ID3v2 lets you define tag restrictions in the extended header, which we can already read/write: https://github.com/Serial-ATA/lofty-rs/blob/8625a129569e9848e4b37800406da391ea79ef49/lofty/src/id3/v2/restrictions.rs But they aren't enforced when writing a tag. Does anyone actually use this feature?...