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
{{ message }}
This repository has been archived by the owner on Nov 24, 2020. It is now read-only.
It seems reasonable, but how the deprecation would be communicated to the targets?
Maybe the deprecation could be informed via documentation, but while JSDoc offers support for documenting function parameters, I don't think it supports object fields. Another option would be to deliver class instances instead of plain JS objects, so that the getter of deprecated fields could warn the developer about it, when not on production mode.
Problem: the need to mark methods as deprecated in order to enforce warning on the clients.
Implementation:
If message is set the client will show it otherwise the message will be: "The method getPlansWithPrice is deprecated"
The text was updated successfully, but these errors were encountered: