-
Notifications
You must be signed in to change notification settings - Fork 36
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
CI_LAB should split message handlers into separate functions #34
Comments
jphickey
added a commit
to jphickey/ci_lab
that referenced
this issue
Feb 7, 2020
Make the patterns in CI better match the patterns used in other modules (CFE core, Sample App, etc) - Separate each command into a separate handler function - Each command handler accepts a const pointer to the full message - Put Telemetry payload into a separate "Payload" sub-structure - Use naming conventions defined in conventions document Note the payload name changes only affect the FSW internal usage, the payload format for the ground system is not changed.
jphickey
added a commit
to jphickey/ci_lab
that referenced
this issue
Feb 7, 2020
Make the patterns in CI better match the patterns used in other modules (CFE core, Sample App, etc) - Separate each command into a separate handler function - Each command handler accepts a const pointer to the full message - Put Telemetry payload into a separate "Payload" sub-structure - Use naming conventions defined in conventions document Note the payload name changes only affect the FSW internal usage, the payload format for the ground system is not changed.
jphickey
added a commit
to jphickey/ci_lab
that referenced
this issue
Feb 8, 2020
Make the patterns in CI better match the patterns used in other modules (CFE core, Sample App, etc) - Separate each command into a separate handler function - Each command handler accepts a const pointer to the full message - Put Telemetry payload into a separate "Payload" sub-structure - Use naming conventions defined in conventions document Note the payload name changes only affect the FSW internal usage, the payload format for the ground system is not changed.
astrogeco
pushed a commit
that referenced
this issue
Mar 9, 2020
Make the patterns in CI better match the patterns used in other modules (CFE core, Sample App, etc) - Separate each command into a separate handler function - Each command handler accepts a const pointer to the full message - Put Telemetry payload into a separate "Payload" sub-structure - Use naming conventions defined in conventions document Note the payload name changes only affect the FSW internal usage, the payload format for the ground system is not changed.
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The "process ground command" routine in CI_LAB processes some commands "inline". This does not match the current/recommended style which is to put command handling into a separate function.
Describe the solution you'd like
Putting each command into a separate function is the preferred CCB style and it improves modularity of the code.
Additional context
All CFE core apps the sample_app all implement the preferred pattern. CI_LAB should be consistent.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: