-
Notifications
You must be signed in to change notification settings - Fork 10
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
Introduce an abstraction layer for the OCM library #6
Comments
Blocked by: #10 |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
This issue has been automatically closed due to the lack of recent activity. |
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. |
This issue has been automatically closed due to the lack of recent activity. |
There should be a set of concrete action items/expectations regarding this topic in order to proceed further. |
Description
For the new CLI, we want to create an abstraction layer shielding the OCM dependency. The abstraction shall provide an API focussing on the functionality we need and internally delegate to the OCM library.
Reasons
This will reduce our code's coupling to the OCM library and make it easier in the future to cope with (breaking) changes within the library.
Attachments
The text was updated successfully, but these errors were encountered: