Resolves ENG-5651.
Made our protos follow the Style Guide.
Details
- Reviewers
varun ashoat - Commits
- rCOMMbc5c70e7e902: Update protos to follow style guide
Built identity, tunnelbroker, commtest, grpc_clients, rust-node-addon and native-rust-library. All CI jobs should pass.
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
I have some questions inline
shared/protos/identity_authenticated.proto | ||
---|---|---|
63–64 ↗ | (On Diff #34916) | IIRC we agreed on consistently using one of prekeys or pre_keys, but I don't remember which one it was. I'll update this diff to make this consistent across all places, now they're both mixed |
shared/protos/identity_client.proto | ||
21–26 ↗ | (On Diff #34916) | @varun, you asked in the Linear comment to rename login to log_in. My reasoning is that "log in" is a verb (RPC call), and "login" is a noun (a message type). I'm not a native though so correct me if I'm wrong, I'm happy to fix these as well |
87–93 ↗ | (On Diff #34916) | |
222 ↗ | (On Diff #34916) | I also recall that we decided to use "device ID" in our codebase and "signing public key" only in Olm-related places so I renamed it here |
Oops, my inline comments are in the previous revision so adding again here
shared/protos/identity_authenticated.proto | ||
---|---|---|
63–64 | IIRC we agreed on consistently using one of prekeys or pre_keys, but I don't remember which one it was. I'll update this diff to make this consistent across all places, now they're both mixed | |
shared/protos/identity_client.proto | ||
21–26 | @varun, you asked in the Linear comment to rename login to log_in. My reasoning is that "log in" is a verb (RPC call), and "login" is a noun (a message type). I'm not a native though so correct me if I'm wrong, I'm happy to fix these as well | |
87–93 | ||
222 | I also recall that we decided to use "device ID" in our codebase and "signing public key" only in Olm-related places so I renamed it here |
Fortunately, we don't use protos in prod yet, except keyserver cron job to update reserved usernames. Hopefully, format of that message hasn't been changed here, so at least in theory it should be fine.
Will we need to "sync" deploys of keyserver and Comm services after landing this diff?
shared/protos/identity_authenticated.proto | ||
---|---|---|
63–64 | I'd agree with this. We got this from Signal, which uses "prekey" (eg. here) |
In theory, we shouldn't have to, as this RPC hasn't been changed, but it's a good idea to do so anyway. I'll ping a heads-up on "Releases and beyond" when landing this