-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
edgehub dispatch message by type #2116
Conversation
604f2de
to
2f470b2
Compare
edge/pkg/edgehub/process.go
Outdated
md = modules.BusGroup | ||
default: | ||
klog.Warningf("msg_group: %s not found", group) | ||
return fmt.Errorf("msg_group: %s not found", group) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the difference of these two implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe the groupMap can be deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use switch-case looks more intuitive, the groupMap structure still used in edgehub currently.
Looks like there's something wrong with the CI/UT |
Yes, I will look at this question. |
2f470b2
to
935121a
Compare
935121a
to
4ac2f21
Compare
The UT problem has been resolved. |
How does the utility be fixed? Looks like has no modification ;-) |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fisherxu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Like the previous way, through array to dispatch message in edgehub is not intuitive, by switch-case grammar will be clearer and maintainable.
Does this PR introduce a user-facing change?:
NONE