shivaam commented on issue #60142:
URL: https://github.com/apache/airflow/issues/60142#issuecomment-4194675332
Quick clarifying question on scope — should **all** required non-boolean
params become positional, even for commands with many required args?
For example, `xcom add` has 5 required params (`dag_id`, `dag_run_id`,
`task_id`, `key`, `value`). Making all of them positional means:
```bash
airflowctl xcom add example_dag "manual__2025-01-01" runme_0 my_key
'{"value": 1}'
```
vs keeping some as flags for clarity:
```bash
airflowctl xcom add example_dag "manual__2025-01-01" --task-id=runme_0
--key=my_key --value='{"value": 1}'
```
Similarly, `dagrun list` has `state` and `limit` as required primitives —
should those be positional too?
Happy to go either way, just want to confirm the intent before submitting
the PR.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
