shivaam commented on issue #69288:
URL: https://github.com/apache/airflow/issues/69288#issuecomment-5099158714
Thanks, both proposals make sense to me. For naming, I agree with keeping
`task()` lowercase because it is a factory method rather than a class or
constructor.
I also like separating generated Airflow options under `spec`, but I would
keep `taskId` explicit and top-level. I find this more self-documenting than a
positional `"extract"`, which could represent an ID, display name, or task
type.
```ts
const extract = pipeline.task({
taskId: "extract",
run: extractFn,
spec: {
retries: 3,
},
});
```
--
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]
