Deprecation warning (API)
See original GitHub issueThe Issue
I don’t get any warnings for deprecated commands usign the api. ( Also api docs are outdated )
Steps to reproduce
- Just call a deprecated command (
send_amount_to_address
) See example: https://github.com/lbryio/lbry/issues/1123#issuecomment-367565815
Expected behaviour
I think the behavior should be consistent across the API and CLI https://github.com/lbryio/lbry/issues/1123#issuecomment-367573379
It should provide / show a deprecation warning / error
:
Deprecated send_amount_to_address in favor of wallet_send
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Deprecating API Endpoints
Deprecation communicates a function, method, or entire package is going away or being. How do you warn developers when an API or endpoint...
Read more >Warning client about deprecated REST API
I would not change anything in the status code or in the service response to be backward compatible. I would add a "Warning"...
Read more >API compatibility policy and deprecation policies
The following notifications are given to mitigate potential issues when APIs are deprecated. The deprecation period is 12 months. ... Notice of API...
Read more >API Best Practices for Feature Deprecation
Deprecating a feature means that we tell our users that they shouldn't use this feature anymore because it will be gone ...
Read more >How and When to Deprecate APIs
Using the @Deprecated annotation to deprecate a class, method, or field ensures that all compilers will issue warnings when code uses that program...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
closing, issue resolved
Thanks. I think the behavior should be consistent across the API and CLI. I probe into the issue.
Kind Regards Amit Tulshyan
On Feb 22, 2018 10:17 AM, “Baltazar Gomez” notifications@github.com wrote: