Repository navigation
feat: show Kalico MCU build configuration - #1979
Merged
pedrolamas merged 1 commit intoOct 9, 2026
Merged
Conversation
Kalico now reports each MCU's firmware build config (mcu_kconfig). Show it in the MCU information dialog when running Kalico. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Pedro Lamas <pedrolamas@gmail.com>
Bundle size report (gzip)
119 chunks compared, 20 changed. Sizes are gzip, matching what nginx serves. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The change is small, follows the existing Kalico-gating and $typedGetters conventions exactly, and all type/getter/locale references were verified to resolve correctly.
0 open findings
What changed in this PR
This PR surfaces Kalico's new per-MCU firmware build configuration (mcu_kconfig, exposed on mcu status objects) in the MCU information dialog on the System page. It adds a "Build Configuration" section that renders the config text when running Kalico and the MCU reports a non-empty value; older firmware reports null, so the section stays hidden.
Changes:
- Add optional
mcu_kconfig?: string | nullto the KlipperMcuStatetype. - Render a new Kalico-gated "Build Configuration" card in
McuInformationDialog.vuevia akconfigcomputed getter. - Add the
build_configurationlocale label and document the feature in the Kalico integrations page.
| File | Description |
|---|---|
| src/typings/klipper.d.ts | Adds mcu_kconfig field to McuState. |
| src/store/printer/types.ts (context) | MCU extends McuState, so it inherits the new field. |
| src/components/widgets/system/McuInformationDialog.vue | New Kalico-gated build-config section with klippyApp/kconfig getters. |
| src/locales/en.yaml | Adds the build_configuration label. |
| docs/docs/features/third-party-integrations.md | Documents the MCU build configuration feature for Kalico. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Kalico now embeds each MCU's firmware build configuration (minimal `savedefconfig` output) in the identify dictionary and exposes it as `mcu_kconfig` on the `mcu` status objects (KalicoCrew/kalico#957).
When running Kalico and the MCU reports it, the MCU information dialog now shows it in a new "Build Configuration" section. Older firmware reports `null`, so the section is hidden.
🤖 Generated with Claude Code