PubInv / PubInv/krake

Firmware, Code Quality, Release Practices , Static Code Analysis with VSCode and PlatformIO, GPAD_API and More Benefits, Demonstrations for Krake Team

Open
#292 7 comments 0 reactions 2 assignees View on GitHub

@nk25719 is already working on this.

Since May 19, 2026.

enhancement
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 am always frustrated when users do not learn the features of a software package.
The migration to PlatformIO and VSCode brings Krake Team Members opportunities to use features the Arduino IDE does not have (Or I never found nor heard mention of). It also means learning some differences and a deficiency(ies).

Static Code Analysis

Please setup and preform Static Code Analysis on the GPAD_API code base and review the analysis as a function of the setup.
For each analysis setup report the analysis of the example Arduino BLINK sketch for comparison.
What are the possible analysis standards or code metrics available?

Unit Testing

Please setup and preform Unit Testing on some example code to demonstrate to Unit Testing to new users.
Show how to add Unit Testing to some simple sketches. For the example Arduino BLINK sketch.
Demonstrate Unit testing on UNO and ESP32

Serial Monitor Features

Demonstrate how to use the Serial Monitor in VSCode.
Compare and contrast to the Serial Monitor in the Arduino IDE.
How to issue commands such as "i' to the target when running GPAD_API
Multiple terminals?
Time Stamp? (Probably not)
Changing COM port on Windows and USBTTY?? on MAC

Custom Board in Platformio.ini file

Should Our Platformio.ini file not have "board = esp32dev" but instead a "board = KRAKE_REV2"?
Where we learn how to make a "board" specific to our exact hardware?

CC:
@nk25719
@RobertLRead

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.