Luca Palmieri

> I am also in a situation where "Extract X-Request-Id header and use that when present OR" would be the preferred option, any reason why you're against this @LukeMathWalker ?...

Client-generated IDs are fine. Using the same type for both client-generated and server-generated is a bad idea. This crate provides a server-generated id. You can add your client generated one...

If you're looking for an example: https://github.com/LukeMathWalker/pavex/blob/main/.github/workflows/release.yml It's the vanilla script generated by `cargo-dist` modified to prepend the nesting prefix `libs/` where necessary to get things to work.

I think the design space is a bit larger than what I can sign myself up to handle right now. Another relevant corner case: there might be multiple workspaces in...

Hey! This behaviour is by design. Generators can be fairly complex and `cargo px` defaults to always invoking the generator, making it responsible for determining if there is any work...

After thinking about this some more, it is not necessary to recompute the codegen plan after _each_ generation. The following should work: - Perform code generation for each leaf in...

It currently doesn't, but I'm open to explore the idea—is there any prior art/research on the topic for `cargo`?

Fixed in [e5eee2e](https://github.com/mainmatter/100-exercises-to-learn-rust/commit/e5eee2e83c683bb520c34f413f5bbfe0c6028dc2), thanks for pointing it out!

Correct, thanks!

Thanks!