[Feature] Allow client to specify declaration order for parameter-handling precedence
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.7k
- Forks
- 2.3k
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 18
Description
Since Click changed its parameter-handling precedence to invocation order rather than declaration order, I've had to apply hideous hacks to force declaration-order precedence. To be clear, I have absolutely no use for invocation-order precedence, and I need completely fine-grained control over parameter precedence (I have a couple dozen options to one of my CLI commands, with tricky dependencies). I'll have to fork Click to work around this if there's no supported way to force declaration-order precedence.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing Click's parameter-handling precedence and determine how a client could select declaration-order precedence or define fine-grained precedence for dependent options; done means a supported, documented behavior that addresses both requested forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100