Envoy: Fix untitled protos in API docs

Created on 8 Oct 2019  路  10Comments  路  Source: envoyproxy/envoy

As per screenshot, there's a bunch of protos that are in the build that don't have human readable title or helpful proto level comments (in some cases). We should do a manual pass over the API docs and fix these.

apv3 aredocs beginner help wanted

Most helpful comment

For whoever works on this, let's please actually enforce this in the proto transform / format tool and then make the format check fail?

All 10 comments

Hi @htuch,
I really want to get involved, but I feel confused about your description. can u give some example of "untitled protos"?

I forgot to attach the screenshot :) Here it is.. the untitled protos are things like "envoy/api/v2/srds.proto", which you can see in this screenshot.
Screenshot 2019-10-18 at 4 57 53 PM

Hi @htuch
I'd like to take it, could u assign it to me?

Hi @htuch,
I am confused about the label "v3 API",
I saw the document, there's only v2 API related stuff.

So my question is this task is for v2 API related proto, right?

@dichen16 correct, we've moved most v2 issues to v3 in preparation for the upcoming v3 support.

Hi @htuch,
I found all the protodoc-title are well defined,
for example,
the protodoc-title of api/envoy/api/v2/srds.proto is HTTP scoped routing configuration,
and the protodoc-title of api/envoy/api/v2/cluster/filter.proto is Upstream filters,

kind confused, Are those protodoc-title fields that this task need to upgrade?

@dichen16 it's the files that are missing protodoc titles that need to be populated, see my example and look at its proto.

@htuch
you mean "envoy/api/v2/srds.proto", is this already well-defined?
Screenshot from 2019-10-24 23-49-51

I think it's kind different with your example, "envoy/api/v2/srds.proto".

For whoever works on this, let's please actually enforce this in the proto transform / format tool and then make the format check fail?

Was this page helpful?
0 / 5 - 0 ratings