-
Notifications
You must be signed in to change notification settings - Fork 51
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
[MNEDC] Refactoring in terms of Architecture #178
Comments
@ayush-kr @suresh-lc What about your opinion (from the contributors' perspective)? |
@t25kim Thank you for a great suggestion. We will estimate its feasibility to migrate the functions of the |
@t25kim @MoonkiHong : We checked this modification. Seem to involve cyclical importing which Go doesn't support. So we are checking on changing the same and testing. |
@suresh-lc Thank you for your prompt analysis. As you suggested, let us discuss further about the best approach once you completed the check-up on changing the same and testing stuff, especially about the cyclical importing which GoLang does not support. We will wait for your updates. ^^ |
Signed-off-by: ayush.kumar <[email protected]>
Signed-off-by: ayush.kumar <[email protected]> - Since MNEDC responsibility is similar to the Discovery Manager, the mnedcmgr package has now been moved inside discoverymgr package and renamed to mnedc.
This issue is still valid since the latest merged PR #178 resolved |
All the implementations have been done |
Sorry. But this has not been resolved yet. |
Ok i get you, lets check this how to go about. |
I think that the mnedcmgr function should be under the discoverymgr since they are similar with respect to functionality.
How about moving the mnedcmgr code under the discoverymgr?
Below should be changed.
Any comments are welcome!
The text was updated successfully, but these errors were encountered: