shahar1 commented on PR #70059:
URL: https://github.com/apache/airflow/pull/70059#issuecomment-5020471054

   > Hi @shahar1,
   > 
   > From my perspective, the value of showing Lang-SDK entrypoint source is 
limited (please check the [#70059 
(comment)](https://github.com/apache/airflow/pull/70059#discussion_r3612734439) 
comment for the code tab example if we support this feature) so the down side 
of this feature is more than the value.
   > 
   > I can still raise the Dev List discussion if you feel the ADR here is not 
enough and we need more stakeholders on this decision.
   > 
   > Thanks.
   
   
   
   > Hi @shahar1,
   > 
   > From my perspective, the value of showing Lang-SDK entrypoint source is 
limited (please check the [#70059 
(comment)](https://github.com/apache/airflow/pull/70059#discussion_r3612734439) 
comment for the code tab example if we support this feature) so the down side 
of this feature is more than the value.
   > 
   > I can still raise the Dev List discussion if you feel the ADR here is not 
enough and we need more stakeholders on this decision.
   > 
   > Thanks.
   
   
   
   > Hi @shahar1,
   > 
   > From my perspective, the value of showing Lang-SDK entrypoint source is 
limited (please check the [#70059 
(comment)](https://github.com/apache/airflow/pull/70059#discussion_r3612734439) 
comment for the code tab example if we support this feature) so the down side 
of this feature is more than the value.
   > 
   > I can still raise the Dev List discussion if you feel the ADR here is not 
enough and we need more stakeholders on this decision.
   > 
   > Thanks.
   
   I think that it's worth a discussion and lazy-consensus mainly due to the 
fact that it's a "no" decision which relates all SDKs, that will be hard to 
challenge in the future - so it should be scoped down exactly to why and what 
it negates.


-- 
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]

Reply via email to