You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Revert Click 6 regressions for chain and deprecate chain #1323
With Click 6.0 we landed a change that was supposed to fix chain (0a2919f). In the process it got worse and broke a bunch of non chain uses.
We should back out that change and instead deprecate chain. I do not believe there is a way to make chain work with the current argument parsing and execution behavior.
The reason for this is that click really wants to delegate the parsing of subcommands with the remainder of the command line but this breaks in the light of chaining. I would need to look into the exact implementation again but last time I investigated this it looked like a fundamental issue we cannot fix with the current design.
@jcrotts did some research and determined that the changes from 6 were already reverted and released in 6.1. After looking over the issues again, we've decided not to remove chain. Putting aside the broad issue of possibly rewriting the parser or pipeline, the open issues appear to be solvable, so we'll continue to address them for now.
Activity
direnter commentedon Jun 1, 2019
Is there a way to mimic
chainfunctionality using traditional Click methods?jtrakk commentedon Jul 19, 2019
davidism commentedon Aug 13, 2020
@jcrotts did some research and determined that the changes from 6 were already reverted and released in 6.1. After looking over the issues again, we've decided not to remove chain. Putting aside the broad issue of possibly rewriting the parser or pipeline, the open issues appear to be solvable, so we'll continue to address them for now.