-
-
Notifications
You must be signed in to change notification settings - Fork 680
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
for CLI parameters
#974
Conversation
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 |
📝 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 |
📝 Docs preview for commit 37cbc85 at: https://f067fbd8.typertiangolo.pages.dev Modified Pages |
shell_complete
and continue to use autocompletion
shell_complete
and continue to use autocompletion
for CLI parameters
📝 Docs preview for commit 5d13465 at: https://df25d00f.typertiangolo.pages.dev Modified Pages |
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.
This is great, thank you! 🙇 🚀
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.