You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Helping the declaration for version that changes a behavior. The idea is to use the version number where something has changed, and proposing a proper function name, rather asking user to handle with comparison operators
Basically, this :
@irrelevant_after("[email protected]", reason="This behavior has been deprecated on version 1.2.3")
is a sugar syntax for
@irrelevant(context.library>="[email protected]", reason="This behavior has been deprecated on version 1.2.3")
Though, name could (should) be more explicit. What about :
@legacy_behavior(deprecated_at="[email protected]", reason="This behavior has been deprecated on version 1.2.3")
The text was updated successfully, but these errors were encountered:
Helping the declaration for version that changes a behavior. The idea is to use the version number where something has changed, and proposing a proper function name, rather asking user to handle with comparison operators
Basically, this :
@irrelevant_after("[email protected]", reason="This behavior has been deprecated on version 1.2.3")
is a sugar syntax for
@irrelevant(context.library >= "[email protected]", reason="This behavior has been deprecated on version 1.2.3")
Though, name could (should) be more explicit. What about :
@legacy_behavior(deprecated_at="[email protected]", reason="This behavior has been deprecated on version 1.2.3")
The text was updated successfully, but these errors were encountered: