RPC transition
Sean Colsen
Team,
I wrote a wiki page to lay out the plans for our RPC API transition.
There are not many hard decisions or design choices in this document yet. Rather it’s a sort of scaffold at the moment which serves to map out the shape of this transition process and give us a place to fill in decisions as we make them. That said, there are a few decisions that Brent and I made last week, for example “always used named parameters”.
Pavish, I think it would be good for you to read this document in full and make sure you don’t have any objections to any of theses plans.
Kriti, you might be interested to skim this document to get a rough sense of this plan since it is currently blocking the beta release.
After we get clarity on special characters in method names, then we can begin filling out our intended function names. I would imagine using the PR process for that so that others can weigh in. We need to get agreement on the patterns we’ll be using before we run wild with implementation.
Brent, once you figure out if we can use special characters in method names, I’d be happy to take a stab at opening a PR that proposes answers to a bunch of our open questions and our function names. Then we could open that PR up for review from other team members in order to move the process along. (Or if you want to open that sort of PR that’s also fine with me.)
