-
Notifications
You must be signed in to change notification settings - Fork 358
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 & typegen deprecation flag for RPCs #5241
Comments
The API contract interfaces itself doesn't use them, it has been converted to state_call, see #5107. Like any other RPC, they could be available or not available, so the API will just decorate the interfaces are existing on |
Makes sense. However, I was hoping we could easily add some deprecation attribute there or something because they are not expected to be there going forward. Otherwise users might think they need to add them when in fact they should just use |
Can certainly add a deprecation attribute (there is no such thing), but this is actually a massive undertaking with typegen and reworking the interfaces. So we are literally months out (probably Q1 2023) before that can even be looked at, just judging by what is in the queue atm. |
In addition to contracts, this would also affect actual RPCs marked as deprecated, eg. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
We will soon remove the contract RPCs from substrate as their are redundant. Please consider removing or deprecating them here and pointing users to
state_call
instead.The text was updated successfully, but these errors were encountered: