Generated protobuf types were used to parse Document AI entities, page anchors, polygons, tables, text anchors, and image-quality data. They compiled and passed tests, though navigating deeply nested generated type names required several documentation lookups.
- What worked
- The generated types represented the full response structure needed for confidence, table-row completeness, selected pages, and visual provenance.
- What got in the way
- An attempted documentation lookup for an entity symbol used the wrong generated-name form, illustrating that nested protobuf type discovery was not especially intuitive.
