[
https://issues.apache.org/jira/browse/AIRFLOW-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689962#comment-16689962
]
Kaxil Naik commented on AIRFLOW-3358:
-------------------------------------
>From what I know and read, click is not fully customizable but I don't have a
>strong opinion. I tried looking on the internet on what others are thinking:
*
https://www.reddit.com/r/Python/comments/73xb5y/click_reviews_should_i_migrate_to_click_from/dntuqlb/
* https://medium.com/@collectiveacuity/argparse-vs-click-227f53f023dc
I would suggest asking this on the mailing list as well to get opinions of
others who have used click and know the pros and cons compared to argparse.
> POC: Refactor command line to use Click
> ---------------------------------------
>
> Key: AIRFLOW-3358
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3358
> Project: Apache Airflow
> Issue Type: Improvement
> Components: cli
> Affects Versions: 2.0.0
> Reporter: Iuliia Volkova
> Assignee: Iuliia Volkova
> Priority: Major
>
> Hi all!
> In one of PR: https://github.com/apache/incubator-airflow/pull/4174 we had a
> talk with Ashb, what will be cool to refactor the cli for getting more
> testable and readable code.
> I want to prepare POC based on one command with implementation with Click and
> covering with tests for discussing Airflow Cli architecture.
> Click already exists in Airflow dependencies.
> Main stimulus:
> - Get more readable and changeable cli - for easy adding command or changing
> commands
> - Get possible to add more tests
> Will be good to know your concerns about such initiative and if there are no
> disagrees about it, I will be happy to start POC
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
