RESTCapabilities undocumented

[m-mohr]

I'm looking at the Python client docs (HTML) and found the capabilities() method, which returns RESTCapabilities.
RESTCapabilities is not documented, search doesn't find it.
How can it be used? Documentation should be added.

Looking at the code reveals how to use it, e.g. con.capabilities().get("federation") but it's not clear from the docs.

[soxofaan]

Indeed RESTCapabilities is not yet included in the docs

In principle it's not hard to add, but I'm bit hesitant to do that at the moment because I'm not really happy with the code architecture around it (and I don't want to over-promise that this is a public API yet).
This is one of the leftovers of the 2018-ish initial design of the package, where you have an abstract Capabilities and a REST-specific implementation RESTCapabilities, but I don't see the point of this inheritance/abstraction.
I'd first want to merge these two classes to a single Capabilities class and make that the public API.

Is this an important/urgent thing for you, or you managed to workaround it and just wanted to signal the bad state of the docs?

[m-mohr]

Just a signal for now.
Came across it when evaluating the compliance of the clients with the Federation Extension:
https://docs.google.com/spreadsheets/d/1GWn53_bLivjLnC-qIGk1rm8GEvCzOesMPKh92E99xL4/edit?usp=sharing

[soxofaan]

I did the simplification/merging of the Capabilities classes in 082a2f5 and added the (still) minimal documentation to the API docs at https://open-eo.github.io/openeo-python-client/api.html#openeo.rest.capabilities.OpenEoCapabilities