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

TestApp: Split DataBrokerEngine Interface into multiple Interfaces #28

Open
wba2hi opened this issue Oct 24, 2023 · 0 comments
Open

TestApp: Split DataBrokerEngine Interface into multiple Interfaces #28

wba2hi opened this issue Oct 24, 2023 · 0 comments
Labels
low priority This issue has a low priority

Comments

@wba2hi
Copy link
Contributor

wba2hi commented Oct 24, 2023

The DataBrokerEngine grows and grows due to the addition of public methods (e.g. VssSpecs + VssPath + connect), we are already over our allowed limit of 10 methods due to this fact. Therefore we should start splitting the logic inside the DataBrokerEngine into multiple objects.

We should try to share code, where code sharing between Java and Kotlin is possible, however we should not do so for suspend functions as Kotlin Coroutines are not supported out of the box by Java.

@Chrylo Chrylo added the low priority This issue has a low priority label Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low priority This issue has a low priority
Projects
None yet
Development

No branches or pull requests

2 participants