[ 
https://issues.apache.org/jira/browse/CASSANDRA-21509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated CASSANDRA-21509:
----------------------------------------
    Description: 
On trunk, paramLabel is display-only: duplicate labels cause no parsing or 
behavioral problem, only ambiguous help output which some time confuses a 
command usage.

The uniqueness rule such as "paramLabels must be unique within a command across 
options, aliases, and positionals is a new convention this ticket introduces, 
not an existing invariant being violated. Its purpose is forward-looking: 
CEP-38 turns these labels into wire keys for cql commands. Enforcing the 
convention on trunk now means no new commands can introduce collisions.

  was:
On trunk, paramLabel is display-only: duplicate labels cause no parsing or 
behavioral problem, only ambiguous help output which some time confuses a 
command usage.

The uniqueness rule such as "paramLabels must be unique within a command across 
options, aliases, and positionals is a new convention this ticket introduces, 
not an existing invariant being violated. Its purpose is forward-looking: 
CASSANDRA-19476 (CEP-38) turns these labels into wire keys in a flat. Enforcing 
the convention on trunk now means no new commands can introduce collisions.


> Enforcing uniqueness of paramLabel across command options
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-21509
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21509
>             Project: Apache Cassandra
>          Issue Type: Task
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>
> On trunk, paramLabel is display-only: duplicate labels cause no parsing or 
> behavioral problem, only ambiguous help output which some time confuses a 
> command usage.
> The uniqueness rule such as "paramLabels must be unique within a command 
> across options, aliases, and positionals is a new convention this ticket 
> introduces, not an existing invariant being violated. Its purpose is 
> forward-looking: CEP-38 turns these labels into wire keys for cql commands. 
> Enforcing the convention on trunk now means no new commands can introduce 
> collisions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to