Open rukai opened 1 year ago
Can you maybe detect that the user is using #[derives] so that you can give an error that makes sense to them?
We could switch the behavior based on the derive
feature but that could be coming in through a dependency, so I'd rather not do that.
In general, the error isn't that great. It especially should say which args / fields are involved.
Please complete the following tasks
Rust Version
rustc 1.69.0 (84c898d65 2023-04-16)
Clap Version
4.2.7
Minimal reproducible code
Steps to reproduce the bug with the above code
cargo run -- orchestrator --help
Actual Behaviour
It gives the panic message:
Expected Behaviour
I've observed that swapping the order of
email
anddomains
fixes the panic but:I expect the error to explain how to fix the issue. Maybe the error makes sense to someone that is familiar with the builder API but I have only ever used the #[derive()] API.
Can you maybe detect that the user is using #[derives] so that you can give an error that makes sense to them?
Additional Context
No response
Debug Output
No response