bolkedebruin commented on PR #51059: URL: https://github.com/apache/airflow/pull/51059#issuecomment-2980588686
@potiuk I concur with the view that we ideally should move these to providers as much as possible (I'm not sure if I was really against that maybe I was ;-) ), except maybe for builtin python (like int, str etc). However, for the sake of simplicity we earlier (in the issue I think) already decided to not ask for providing a plugin implementation. I think that warrants a separate PR. So yes you are right, but given that pydantic is used elsewhere in airflow-core I don't think we are adding extra dependencies into core right now and that we can move it as an improvement by a follow up. This PR actually improves the API that the plugins should follow (cls instead of classname). The PR implementing the plugin separation can use that. -- 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]
