Test & adjust newly updated .clang-tidy rules. Resolve all user fixable warnings/diagnostics. Also format all cpp and hpp files (many were not formatted).
What changed
All files are formatted, some snippits have format disabled due to less readable format.
Resolve warnings where possible, improved consistency by a lot.
Remove/adjust format and tidy rules wherever needed. Some rules were too agressive or not to our liking.
Some snippits had improvements left on the table. Some examples are tickingservice.cpp nesting reduction or strokecanvasrenderer.cpp qreal instead of float values.
CI/CD ignores compile errors that are not related to user written code.
ci-image.yml adjustment requiring node and docker with registry token to access docker build.
Caution
Functionality should not change, but verifying if things messed up is important due to large change overal (excluding formatting as well).
Take into account other PR's, conflicts could occur.
### Goal
Test & adjust newly updated `.clang-tidy` rules. Resolve all user fixable warnings/diagnostics. Also format all cpp and hpp files (many were not formatted).
### What changed
- All files are formatted, some snippits have format disabled due to less readable format.
- Resolve warnings where possible, improved consistency by a lot.
- Remove/adjust format and tidy rules wherever needed. Some rules were too agressive or not to our liking.
- Some snippits had improvements left on the table. Some examples are `tickingservice.cpp` nesting reduction or `strokecanvasrenderer.cpp` qreal instead of float values.
- CI/CD ignores compile errors that are not related to user written code.
- `ci-image.yml` adjustment requiring node and docker with registry token to access docker build.
### Caution
- Functionality should not change, but verifying if things messed up is important due to large change overal (excluding formatting as well).
- Take into account other PR's, conflicts could occur.
One finding I had is that when building and running feat/settings-revamp branch, config file adds anim. This seems to cause issues on main and tidy-warning-fixes.
On request, I will remove (most) comments in the codebase.
One finding I had is that when building and running `feat/settings-revamp` branch, config file adds anim. This seems to cause issues on `main` and `tidy-warning-fixes`.
On request, I will remove (most) comments in the codebase.
I wanted to illustrate that I noticed that building feature branch adds/changes config file. The new additions seemingly break compatibility with main and tidy-warning-fixes.
anim refers to the added appearance { anim { block in config.json.
That is unclear indeed.
I wanted to illustrate that I noticed that building feature branch adds/changes config file. The new additions seemingly break compatibility with main and tidy-warning-fixes.
anim refers to the added `appearance { anim {` block in `config.json`.
zach
merged commit 60831de7c5 into main2026-06-30 14:46:39 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Test & adjust newly updated
.clang-tidyrules. Resolve all user fixable warnings/diagnostics. Also format all cpp and hpp files (many were not formatted).What changed
tickingservice.cppnesting reduction orstrokecanvasrenderer.cppqreal instead of float values.ci-image.ymladjustment requiring node and docker with registry token to access docker build.Caution
4023a2fb01to4a18edfc78tidy warning fixesto tidy, format, and resolving tidy warningsOne finding I had is that when building and running
feat/settings-revampbranch, config file adds anim. This seems to cause issues onmainandtidy-warning-fixes.On request, I will remove (most) comments in the codebase.
What does this mean?
That is unclear indeed.
I wanted to illustrate that I noticed that building feature branch adds/changes config file. The new additions seemingly break compatibility with main and tidy-warning-fixes.
anim refers to the added
appearance { anim {block inconfig.json.