Skip to content

don't complete args that start with dash after double dash separator#1248

Merged
davidism merged 1 commit into
pallets:7.xfrom
bertolinocastro:master
Feb 27, 2020
Merged

don't complete args that start with dash after double dash separator#1248
davidism merged 1 commit into
pallets:7.xfrom
bertolinocastro:master

Conversation

@bertolinocastro
Copy link
Copy Markdown
Contributor

@bertolinocastro bertolinocastro commented Mar 2, 2019

Preventing Click from trying to complete args that starts with dash after a double dash separator

fixes #1247

@davidism
Copy link
Copy Markdown
Member

davidism commented Mar 2, 2019

Needs test and change log.

@bertolinocastro
Copy link
Copy Markdown
Contributor Author

I ran the py.test and tox tests as stated here and I got this fail that seems to already occur before my changes:

tests/test_chain.py::test_multicommand_chaining XFAIL

However, I'm not familiar with those applications and automated testing. So I can't go any further.

Please tell me if I can help with anything else.

@davidism
Copy link
Copy Markdown
Member

davidism commented Mar 2, 2019

You need to add a test and changelong entry for the behavior you changed. That is an xfail message about other code, it's not an error.

Comment thread CHANGES.rst Outdated
Comment thread tests/test_bashcomplete.py Outdated
@bertolinocastro
Copy link
Copy Markdown
Contributor Author

Sorry for that many commits.

I just see that my last commit was decorating the wrong function. I'm going to correct that.

@bertolinocastro
Copy link
Copy Markdown
Contributor Author

I think that everything is fine now. Anything else?

Are that many commits a problem? Should I make a new PR from a bare fork with these modifications?

@bertolinocastro
Copy link
Copy Markdown
Contributor Author

Closing, as it seems that no one is caring about this issue.

@davidism davidism reopened this Mar 13, 2019
@ThiefMaster
Copy link
Copy Markdown
Member

Closing, as it seems that no one is caring about this issue.

No need for passive-aggressive comments. While everyone loves it when PRs get reviewed and merged within hours, please keep in mind that for most open source projects - including this one - the maintainers do this mostly in their free time.

Are that many commits a problem? Should I make a new PR from a bare fork with these modifications?

No, we can squash when merging. Or you can squash them in git (via interactive rebase) and force-push.
But for future PRs it's a good idea to use a separate branch instead of master in your fork.

Comment thread tests/test_bashcomplete.py Outdated
Comment thread tests/test_bashcomplete.py
Comment thread CHANGES.rst Outdated
@bertolinocastro
Copy link
Copy Markdown
Contributor Author

I am really sorry if my last message sounded a bit rude. It was not my intention.

ASAP I will push the finished changes here. I thank you all for your help.

@bertolinocastro bertolinocastro force-pushed the master branch 3 times, most recently from 3353b70 to c557d85 Compare March 16, 2019 04:09
@bertolinocastro
Copy link
Copy Markdown
Contributor Author

Please, let me know if anything else is needed. Thank you in advance.

@davidism davidism changed the title Fixes #1247 don't complete args that start with dash after double dash separator Feb 23, 2020
@davidism davidism dismissed stale reviews from ThiefMaster and themself February 23, 2020 23:22

outdated

@davidism davidism added the f:completion feature: shell completion label Feb 24, 2020
@davidism davidism added this to the 7.2 milestone Feb 24, 2020
@davidism davidism changed the base branch from master to 7.x February 27, 2020 03:13
@davidism davidism modified the milestones: 7.2, 7.1 Feb 27, 2020
@davidism davidism merged commit 29e7de5 into pallets:7.x Feb 27, 2020
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Nov 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

f:completion feature: shell completion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bash completion understands options even after "--"

3 participants