Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge Capabilities and RESTCapabilities #611

Open
soxofaan opened this issue Aug 29, 2024 · 1 comment
Open

Merge Capabilities and RESTCapabilities #611

soxofaan opened this issue Aug 29, 2024 · 1 comment

Comments

@soxofaan
Copy link
Member

This came up while looking into #610:

# TODO Is this base class (still) useful?
class Capabilities(ABC):
"""Represents capabilities of a connection / back end."""

in python client we have openeo.capabilities.Capabilities and openeo.capabilities.rest.RESTCapabilities. This still stems from initial 2018-ish design of the openeo package, but I don't see the point of the abstraction here. I think we're better off with just a single Capabilities implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant