Looking into the doc-generation error.

Looking into the doc-generation error.

Fixed

I'm curios though, what's the benefit of the split in multiple files?

Nothing, from the perspective of rust or python. It is just cosmetic.
Although, I feel pagination/pagination_info.proto and pagination/pagination_params.proto displays the scope better. The same applies to bounds.proto and metric_sample.proto. This is also what how the files in the google api submodule are organized.

I'm curios though, what's the benefit of the split in multiple files?

Nothing, from the perspective of rust or python. It is just cosmetic. Although, I feel pagination/pagination_info.proto and pagination/pagination_params.proto displays the scope better. The same applies to bounds.proto and metric_sample.proto. This is also what how the files in the google api submodule are organized.

Evidently, I was incorrect about python (correct about rust though). In python, the file name gets treated as the package name, so it creeps into the import paths as well. I still feel that splitting up files still adds more structure to the messages. So I would still go ahead with this, to keep things moving. If needed, we can of course look into re-organizing it before making the first major release.

Personally I don't mind the extra package in Python, to be honest it already looks ugly in Python with the _pb2 suffix and all, and in general we want to abstract all this away in the SDK anyway, so this would only affect SDK developers or people wanting to access the APIs directly.