search

Shinmera / tooter

A Common Lisp client library for Mastodon instances.
https://shinmera.github.io/tooter
zlib License
44 stars 6 forks source link

Added print object tag history #17

Closed cage2 closed 4 years ago

cage2 commented 4 years ago

Hi Shimera!

Additionally to this PR i have a question: what to do if a entry point of the API is deprecated upstream?

In a future PR should i just replace the deprecated method with a compliant one even if it does change this library API in a way that requires user of tooter to change their code?

Bye! C.

Shinmera commented 4 years ago

Good question. If the semantics of tooter's API can be preserved by converting data or whatever, then we should naturally switch to the newer API calls that are not deprecated without needing to bother the user.

If that is not possible, I would recommend creating new functions that fit the new API, leaving the old ones intact, and just mentioning their deprecation status in the documentation.

cage2 commented 4 years ago

On Wed, Apr 22, 2020 at 06:25:42AM -0700, Nicolas Hafner wrote:

Hi!

Good question. If the semantics of tooter's API can be preserved by converting data or whatever, then we should naturally switch to the newer API calls that are not deprecated without needing to bother the user.

If that is not possible, I would recommend creating new functions that fit the new API, leaving the old ones intact, and just mentioning their deprecation status in the documentation.

very well, i think this is a wise solution, however i wonder which names could be chosen for the new functions if there is a name clash, honestly i have no idea. Anyway this is not something i actually met until now so the problem could be postponed. :-)

Bye! C.