Ed Page 15616bbd13 fix(error): Remove usage from value validation ... When to show usage? We are currently mixed about it. For `validator`, we didn't show it at all. Sometimes we show the used arguments and sometimes we don't. With `ValueParser`, I ran into the problem that we weren't showing the used arguments like we had previously in some cases. In deciding how to solve this, I went with the simplest route for now and removed it as the usage likely doesn't add much context to help people solve their problem, more so the recommendation for help. We'll see how the feedback is on this and adjust.		2022-05-23 20:56:04 -05:00
..
builder	fix(error): Remove usage from value validation	2022-05-23 20:56:04 -05:00
derive	feat(derive): Opt-in to inferred value_parser	2022-05-20 19:25:20 -05:00
derive_ui	feat(derive): Allow users to opt-in to ValueParser	2022-05-20 15:38:44 -05:00
ui	test(output): Ensure correct streams	2022-04-22 10:56:47 -05:00
app.yml	fix: Revert as much yaml policy to v2 as possible	2021-12-02 16:06:21 -06:00
derive_ui.rs	test: Re-enable ui tests	2022-05-20 14:10:32 -05:00
examples.rs	feat(multicall): Stablize multicall	2022-05-20 12:20:40 -05:00
macros.rs	fix(macros): Allow dashed values (#3699)	2022-05-06 10:58:00 -05:00
ui.rs	feat(multicall): Stablize multicall	2022-05-20 12:20:40 -05:00
yaml.rs	refactor: Update app variables to cmd	2022-02-14 15:55:56 -06:00