PubInv / PubInv/krake

Firmware Quality, Review All Include Files For Redundancy and Optimum Placement

Open
#177 0 comments 0 reactions 2 assignees View on GitHub

@ForrestErickson is already working on this.

Since Jul 5, 2025.

good first issue help wanted
Dominant language
C++
Stars
8
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
_A clear and concise description of what the problem is.

Ex. I'm always frustrated when I do not know if and where an include file is needed.

Describe the solution you'd like
A clear and concise description of what you want to happen.
Review of the GPAD_API firmware project #include statements to remove any unnecessary libraries.
Develop optimum placement of #include statements in project files.
Are there practices like "guards" good programmers (we) should be adopting?

Are their software quality tools for automated review?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.