Use Serde to parse YAML input #853
Comments
|
Thanks for the detailed write up! I'm 100% for this if it can be made in a backwards compatible way, if not 3.x shouldn't be too far on the horizon and would accept a PR to the I'll mark this as "help wanted" simply because my bandwidth is limited right now with work and would be more than willing to take a look at a PR on the matter. Once I knock out a few more issues and my bandwidth opens back up, I'll take a swing at implementing this if it hasn't been done already 😉 |
|
Blocker: dtolnay/serde-yaml#94 |
|
#1041 would help with the lifetime blocker |
|
We have decided to deprecate the YAML API. For more details, see #3087. If there is interest in a YAML API, it will likely be broken out into a |
The errors from
clapwhen my YAML isn't perfect are far less helpful than they could be. This makes it difficult to iterate on a YAML input.Using Serde to read the YAML, errors would be able to provide the line, column, and property path at which the error occurs.
Steps to reproduce the issue
Actual clap error
(this seems like a bug)
Serde-style error
Current clap error
Serde-style error
Current clap error
Serde-style error
The text was updated successfully, but these errors were encountered: