Closed paulius-valiunas closed 1 week ago
Maybe add a section in NextVersion.md saying the interface is deprecated
should the PresentationRpcInterface class itself also be marked as deprecated?
should the PresentationRpcInterface class itself also be marked as deprecated?
people still need a way to register it in their frontend/backend, so I can't just deprecate it... we would need to provide an alternative registration path, but that would be a big refactor and I think it's fine to just keep things this way for now. Once we move all the existing APIs, we can then deprecate RPCManager
and related classes, as well as the RPC interfaces themselves. But at that point, we will probably be close to 6.0 where we can actually remove all the deprecated methods, so there wouldn't be any actual code in the deprecated interfaces.
This pull request is now in conflicts. Could you fix it @paulius-valiunas? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
This pull request is now in conflicts. Could you fix it @paulius-valiunas? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/
@mergifyio backport release/4.10.x
@mergifyio backport release/4.11.x
backport release/4.10.x
backport release/4.11.x
We are planning to deprecate RPC altogether in the future, and while we don't have a replacement just yet, we can at least encourage people to use various wrappers instead of calling RPC interfaces directly. This way the transition to new APIs will be less disruptive. Presentation is the only RPC interface where all the methods are public and not internal.