Skip to content
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

Remove requirements for message initialization "clear" vs "no-clear" options #1713

Closed
skliper opened this issue Jul 26, 2021 · 1 comment · Fixed by #1720 or #1701
Closed

Remove requirements for message initialization "clear" vs "no-clear" options #1713

skliper opened this issue Jul 26, 2021 · 1 comment · Fixed by #1720 or #1701
Assignees
Labels
docs This change only affects documentation. requirements
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Jul 26, 2021

Is your feature request related to a problem? Please describe.
CFE_MSG_Init no longer supports "clear" vs "no-clear" options due to abstraction incompatibilities.
cSB4315.1 - SB: Initialize Message - Clear
cSB4315.2 - SB: Initialize Message - No Clear

Describe the solution you'd like
Remove these "special option" requirements. The requirement is that it initializes the packet (cSB4315), the design/implementation describes the exact behavior (there are many possible compliant implementations by design). Ambiguous options that can not be abstracted should be avoided in the API.

Describe alternatives you've considered
None

Additional context
None

Requester Info
Jacob Hageman - NASA/GSFC

@skliper skliper added docs This change only affects documentation. requirements labels Jul 26, 2021
@skliper skliper added this to the 7.0.0 milestone Jul 26, 2021
@skliper skliper self-assigned this Jul 26, 2021
skliper added a commit to skliper/cFE that referenced this issue Jul 28, 2021
astrogeco added a commit that referenced this issue Jul 28, 2021
paulober pushed a commit to paulober/cFE that referenced this issue Aug 1, 2021
@astrogeco
Copy link
Contributor

Closed by #1701 and #1720

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change only affects documentation. requirements
Projects
None yet
2 participants