[Feature]: Ozone endpoints

[pupi1985]

Is your feature request related to a problem?

This is mainly a question but could work as a feature request. I will need to consume ozone endpoints. I understand they have not yet been implemented in the SDK. This means I will have to implement them on my own (buh... work!).

Describe the solution you'd like

Ideally, the SDK would implement these endpoints.

Describe alternatives you've considered

I'm wondering if there is anything I could reuse from the SDK or if I should just fall back completely to raw HTTP requests. Thanks for your support.

Priority

Low

Implementation ideas

No response

Additional context

No response

[edevsh]

Thank you for your suggestion, @pupi1985.

Currently, my focus is on implementing only the most critical endpoints, as the SDK is still in its beta stage, and the API interface has not yet reached full stability. I am actively working on the 2.x/stable version to address these challenges.

If you're interested in contributing, a PR for these endpoints targeting the 2.x version would be greatly appreciated. However, my immediate priority is not adding new endpoints or features but refactoring existing issues to create a more maintainable codebase.

Current Issues and Challenges:

• Traceability is in a poor state (see issue: [Enhancement]: Enhance Traceability  #32).
• Adding new endpoints, especially implementing endpoint-specific casting components, is unnecessarily complex.
• The SDK's reliance on inheritance over composition has introduced difficulties in extending functionality.

Potential Improvements:

• Adopting PSR standards to align with modern development practices.
• Enabling "strict types" to enhance stability and reduce errors.
• General enhancements to improve maintainability and extensibility.

Thank you for your understanding, and I welcome your contributions or further feedback!