Alexander Reynolds

Both of your comments helped me understand the difference between the channel message encoding and schema encoding better; thanks for that! It makes sense that the channel message encoding could...

@defunctzombie yeah, your second paragraph was my reasoning for the PR as it was initially proposed. Since "mime" isn't an encoding I agree with the above consensus that a schema...

Some prior art from gRPC, a typical call uses `application/grpc+proto` (not registered with IANA). from https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md#requests: > Content-Type → "content-type" "application/grpc" [("+proto" / "+json" / {custom})]

@defunctzombie you're right that the attachment field name is not the same as this issue. For now, we have standardized on accepting a mimetype as the message encoding, with no...

Bumping this, would be really interested here as well. We have way too many protos to comfortably fit on one page, so the per-folder or per-package approach with cross-linking would...

I think I found an issue with the generated links for nested message definitions. If you have ``` message Outer { message Inner { } Inner inner = 1; }...

@sbidoul Sure thing. For clarity I mean "offline install of a package which has a VCS URL dependency" I created a repo with an explanatory README here: https://github.com/alkasm/vcs-url-install-example edit: lol...

> I think this is the key statement Yep, sorry I think my initial description dived into the details too quickly. I added that as a first line for clarity....

@sbidoul Thanks for re-opening then (should also remove the duplicate tag in that case?). I think I still agree with @pradyunsg that the suggested solution in https://github.com/pypa/pip/issues/5780#issuecomment-678676463 would solve my...

> I’m conflicted on this particular case. The VCS URL in the example repo is pointing to a variable location (the default branch), and if I remember correctly, there are...