-
-
Notifications
You must be signed in to change notification settings - Fork 675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ποΈ Deprecate shell_complete
and continue to use autocompletion
#974
base: master
Are you sure you want to change the base?
Conversation
β¦ will be removed
shell_complete
and continue to use autocompletion
shell_complete
and continue to use autocompletion
π Docs preview for commit 749cade at: https://6b09d267.typertiangolo.pages.dev Modified Pages |
π Docs preview for commit 286b94e at: https://b744c2ac.typertiangolo.pages.dev Modified Pages |
π Docs preview for commit ca4ca2c at: https://214d2bbc.typertiangolo.pages.dev Modified Pages |
@@ -1,28 +1,18 @@ | |||
from typing import List | |||
|
|||
import click |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure we still need this file even, it seems like most of the other functionality here is tested in other unit tests as well?
π Docs preview for commit 2261391 at: https://bde7f85a.typertiangolo.pages.dev Modified Pages |
π Docs preview for commit e17a0f5 at: https://b6cd9db3.typertiangolo.pages.dev Modified Pages |
Cf issue: #949
After some internal discussion with Tiangolo, we've decided to keep the
autocompletion
functionality in Typer as-is, to ensure minimal breaking changes for users. This also means that we won't be moving to a new argumentshell_complete
, as Click v8 has done.While there were some preliminary provisions for
shell_complete
already in the code base, this functionality wasn't really documented or supported yet, and it didn't yet rely on type annotations, so we consider it to have been non-functional, and we'll remove it in a later version.This PR clarifies the deprecation status both in the code, in a warning message, and in the docs.