shivaam commented on issue #69288:
URL: https://github.com/apache/airflow/issues/69288#issuecomment-5098825085
> I'd also like to remove `registerTask` and introduce `registerDags(d1,
d2)` as the entrypoint.
Before removing `registerTask`, I think we should clarify one compatibility
question: does native TypeScript Dag authoring replace the existing Python
`@task.stub` Dag with TypeScript handlers, or should the SDK continue
supporting both modes?
If both remain supported, we could keep `registerTask()` as a compatibility
API and use `registerDags()` only for complete TypeScript-authored Dags.
Alternatively, we could provide a new API:
```ts
registerHandlers("sales_pipeline", {
extract: extractFn,
transform: transformFn,
});
```
I would avoid making `registerDags()` accept a special pseudo-Dag for a
Python-defined Dag. TypeScript does not own that Dag’s schedule or dependency
graph, so treating its handlers as a Dag could make the source of truth unclear.
--
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]
