Suraj-kumar00 commented on PR #67947: URL: https://github.com/apache/airflow/pull/67947#issuecomment-5709749901
> > cc @ashb @bugraoz93 @potiuk @Suraj-kumar00 > > Following up on [the naming discussion in the review thread](https://github.com/apache/airflow/pull/67947#discussion_r3558522389) (`TasksOperations` vs `TaskInstanceOperations` — "these are TaskInstance operations" vs "match core CLI naming"), where Ash suggested taking it to the dev list: > > I have started that discussion: **https://lists.apache.org/thread/32oqb3j7f22mlj12t2q95f5n4fqzhlcp** > > It frames the general question — should the user-facing command surface align with REST API resources, or keep parity with the `airflow` CLI — with the seven open task-command PRs (this one included) as the concrete motivation. > > Since the class name here directly determines the user-facing command group, it may be worth reaching consensus there first before merging this PR — that would avoid shipping the commands under a name that might immediately need a breaking rename. > > Awesome, thanks for creating the discussion! Hello @bugraoz93 @BobDu, Is there any update on this, I can see the discussion but i'm not able to comment on this. How are we handling this are upto any conclusion? -- 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]
