Can positional arguments be in any order? （Like dig command）

[mokeyish]

The dig command can be like this, query-type and domain can be in any order. Does clap support arbitrary ordering of positional arguments?

The dig command supports:

1. dig aaaa google.com
2. dig google.com aaaa

#[derive(Parser, Debug)]
#[command(author, version, about, long_about = None)]
pub struct ResolveCommand {
    /// is in the Domain Name System
    #[arg(value_name = "domain")]
    domain: Domain,

    /// is one of (a,any,mx,ns,soa,hinfo,axfr,txt,...)
    #[arg(value_name = "q-type", default_value = "a", value_parser = parse_query_type)]
    q_type: QueryType,

    /// is one of (in,hs,ch,...)
    #[arg(value_name = "q-class", default_value = "in", value_parser = parse_query_class)]
    q_class: QueryClass,
}

---

I want clap to try to parse the QueryType first, then the QueryClass, and finally the Domain.

Can be in any order, but only parsed once.

[epage]

No, positionals are strictly ordered. Relying on parser success to try other options works in very limited cases, can be confusing, and would generate bad error messages.

[mokeyish]

Is it possible to group these arguments into one group? The arguments in the group can be configured in any order. If the parsing is successful, it will be returned. If an error occurs, it will be reported in strict order.