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

Update header files to follow current convention #150

Closed
jphickey opened this issue Oct 6, 2023 · 0 comments · Fixed by #151
Closed

Update header files to follow current convention #150

jphickey opened this issue Oct 6, 2023 · 0 comments · Fixed by #151
Assignees

Comments

@jphickey
Copy link
Contributor

jphickey commented Oct 6, 2023

Is your feature request related to a problem? Please describe.
A convention/pattern for header file content was documented in nasa/cFE#2306, and is being further refined in nasa/cFE#2451

Describe the solution you'd like
SCH_LAB should follow the documented naming convention

Additional context
All components should be consistent

Requester Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this Oct 6, 2023
jphickey added a commit to jphickey/sch_lab that referenced this issue Oct 6, 2023
Move configurable header files into a separate directory with names
according to the pattern documented in CFE.
jphickey added a commit to jphickey/sch_lab that referenced this issue Oct 6, 2023
Move configurable header files into a separate directory with names
according to the pattern documented in CFE.
jphickey added a commit to jphickey/sch_lab that referenced this issue Oct 6, 2023
Move configurable header files into a separate directory with names
according to the pattern documented in CFE.
jphickey added a commit to jphickey/sch_lab that referenced this issue Oct 6, 2023
Move configurable header files into a separate directory with names
according to the pattern documented in CFE.
dzbaker added a commit that referenced this issue Oct 30, 2023
Fix #150, implement header file convention for SCH_LAB
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant