Skip to content
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

Add new standards for deprecating APIs #1365

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

ndrluis
Copy link
Collaborator

@ndrluis ndrluis commented Nov 23, 2024

Solves #1330.

@Fokko, could you check if I got the License and file headers right?

@ndrluis
Copy link
Collaborator Author

ndrluis commented Dec 11, 2024

Some Deprecation Examples

Future Deprecation
image

Deprecated
image

Missing to remove
image

help_message="Support for parsing catalog level identifier in Catalog identifiers is deprecated. Please refer to the table using only its namespace and its table name.",
deprecate_in="0.8.0",
remove_in="0.9.0",
topic="Please refer to the table using only its namespace and its table name.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ndrluis Sorry for not getting to this earlier. My main concern is that we might make things more complex than necessary. Why would we not use the addendum here? I find the prefix and topic not very intuitive, as in, it is not directly obvious to me how the deprecation warning will look like. That raises the question, should we reduce the number of options?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed the topic attribute to 'addendum' and will improve the documentation to clarify the output message for each case.

@ndrluis ndrluis requested a review from Fokko December 11, 2024 18:38
@ndrluis ndrluis marked this pull request as ready for review December 11, 2024 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants