-
Notifications
You must be signed in to change notification settings - Fork 1
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
Adds command-specific event types. #29
Conversation
Discussed in OneSDK Friday meeting: comment out the event types for commands that are not refactored yet so they do not show as available. cc: @aduane |
|
||
// Specific Command events | ||
|
||
ADJUST_DIAGNOSIS_COMMAND__PRE_COMMAND_ORIGINATE = 1000; |
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.
Can we change these to remove the second "COMMAND"? Seems redundant.
Example:
ADJUST_DIAGNOSIS_COMMAND__PRE_COMMAND_ORIGINATE = 1000; | |
ADJUST_DIAGNOSIS_COMMAND__PRE_ORIGINATE = 1000; |
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.
@aduane I like it better if we remove the first COMMAND and keep the second one. The reason for this is that they match the naming of the canvas-core command events, which are named PreCommandOriginate
, PostCommandOriginate
, etc. How about ADJUST_DIAGNOSIS__PRE_COMMAND_ORIGINATE
?
7cc332f
to
2bf70f1
Compare
5d8928f
to
aa81b3d
Compare
https://canvasmedical.atlassian.net/browse/KOALA-1276