Fix #107, Convert command success events to INFORMATION type
#110
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Describe the contribution
INFOtype rather thanDEBUGwhich is the nominal pattern across cFE/cFS although currently there are a couple of apps that don't comply, and a couple of cFE components that only partially comply.Note: cFE and most (but not all) apps leave the Reset command as
DEBUG- should this remain the case, or should it be changed as well toINFOas the operator might still want to be informed that the Reset command occurred successfully whenDEBUGevents are turned off.Testing performed
GitHub CI actions all passing successfully (incl. Build + Run, Unit/Functional Tests etc.).
Expected behavior changes
Align command event types to cFS guidelines as per cFE Developer's Guide s7.2
Contributor Info
Avi Weiss @thnkslprpt