ussserrr
ussserrr
### Discussed in https://github.com/ussserrr/stm32pio/discussions/113 Originally posted by **FrankBau** February 5, 2022 Warning: GPDSC generation will be soon discontinued With STM32CubeMX 6.4.0 (Nov. 2021) I get a warning on code generation: ...
Establish broad set of static checkers like: - [ ] mypy - [ ] black - [ ] flake and so on.
Illustration, something like ```shell script $ stm32pio new -b nucleo_f031k6 --with-build ...actual non-verbose output here... $ ll ...actual output here... ```
During prolonged operations (like CubeMX code generation) show the subprocess state/last log line so a user can know whether it stalled or not, especially on non-verbose mode.
If we analyze `.ioc` file closely, some useful properties can be found: - [ ] We can set `project couplefilesbyip ` and `project toolchain ` automatically instead of asking a...
Currently, validation process of some tool is described completely separately of its class (PlatformIO and CubeMX, Java can be treated as a part of CubeMX actually): ```python return ToolsValidationResults( Tool(name=param,...
Currently, these operations are independent of each other and scattered around the code which can lead to potential inconsistencies. Actions and their options can be represented as classes with explicit...
- [ ] Consider PlatformIO-like schema: only explicitly stated options should be stored in the actual config file - [ ] Use getters like `getboolean`/`getint` (no more `yes_options`/`no_options`/..., but need...
For example, see [Google style guides](https://google.github.io/styleguide/pyguide.html). - [ ] Annotate exceptions (this rises ...)