Add a component image generator

[Sebbeben]

Component value calculator & image generator

Adds a Value calculator tool (Tools menu) that decodes/encodes the value of common components and generates a clean SVG picture you can attach to a part — handy for assortments (e.g. AliExpress kits) imported with blank thumbnails and sparse data.

Calculator tabs

Each tab is a bidirectional decoder/encoder, draws the part to the selected package with a collapsible "appearance" panel, and can attach the rendered image (optionally as the master picture):

• Resistor — 4/5/6-band colour code
• Capacitor — value ↔ 3-digit code ↔ tolerance
• SMD resistor — value ↔ 3-digit / 4-digit / EIA-96 code
• Inductor — colour-band code
• SMD inductor — value ↔ µH code

Bulk "Generate component images" (parts-table action)

• Classifies each selected part (resistor / capacitor / inductor / diode / LED, THT or SMD) with ComponentValueGuesser and detects value, voltage, tolerance, power, ppm, pitch, diameter, colour, SMD package and marking from the name, description and parameters.
• Renders a preview per part, lets you tweak appearance, and attaches the images in one go.
• Can also write matching KiCad symbol/footprint/reference-prefix EDA fields for the whole selection.

Implementation

• ComponentValueGuesser — classification + detection + EDA suggestion.
• GeneratedImageAttachmentHelper — stores the SVG through the existing attachment pipeline, so every generated image is run through the SVG sanitizer on save.
• Two POST endpoints on PartController (generate_image, set_eda) guarded by edit + CSRF.
• New @tools.value_calculator permission, a Tools-tree entry, and docs.
• All drawing is client-side in a Stimulus controller; the un-sanitized live preview escapes part-derived text and validates colours as defence-in-depth.

Tests

Unit tests for ComponentValueGuesser and functional tests for the endpoints, including permission/CSRF enforcement and the persisted side effects.

Open question for review

The tool is currently called a "calculator", but roughly half its value is image generation for real parts, and some tabs are really decoders/converters. Happy to rename or restructure (e.g. "Component value & image tool", or split "Decoder" vs "Image generator") — whatever fits Part-DB best.

Screenshots

[codecov]

Codecov Report

❌ Patch coverage is 85.96803% with 79 lines in your changes missing coverage. Please review.
✅ Project coverage is 60.30%. Comparing base (cd4b5aa) to head (0dac22b).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
src/Services/Tools/ComponentValueGuesser.php	90.55%	34 Missing ⚠️
src/Controller/ToolsController.php	84.00%	16 Missing ⚠️
...ces/Attachments/GeneratedImageAttachmentHelper.php	70.45%	13 Missing ⚠️
src/Controller/PartController.php	78.26%	10 Missing ⚠️
src/Services/Parts/PartsTableActionHandler.php	14.28%	6 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1435      +/-   ##
============================================
+ Coverage     59.77%   60.30%   +0.53%     
- Complexity     9103     9334     +231     
============================================
  Files           679      681       +2     
  Lines         29618    30181     +563     
============================================
+ Hits          17703    18200     +497     
- Misses        11915    11981      +66     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jbtronics]

Im not sure if i find the term "Value calculator" so fitting for it.
Its generating an image out of an given value, not calculates a value out of some codewords from an image.

[Sebbeben]

You're right that "Value calculator" mis-describes it — thanks for flagging. It actually does two related things, and the name should make that clearer:

1. Bidirectional code ↔ value conversion (the tabbed part). It works both ways: pick a resistor's colour bands / type an SMD 103 / a capacitor 104 and it decodes the value — or enter a value and it produces the matching bands/code. (It decodes the codewords you type, not a photo — there's no image recognition.)

2. Image generation: from that value — or, in bulk, from a selection of existing parts — it renders a labelled SVG of the component and attaches it as the part picture. That's the main motivation: assortment kits often import with blank thumbnails and almost no data.

So a "codeword → value" direction does exist, but I agree the image generation is the headline and the current name hides it. Renaming options:

• Component image generator — with the code ↔ value conversion as an input helper inside it
• Component code & image tool
• Split it conceptually into a "Code ↔ value decoder" and an "Image generator"

Do you have a preference? Happy to rename the tool, its route, permission and menu entry to match.

PS — I've added screenshots to the PR description above (the calculator tabs + the bulk "generate images" review page) so the two halves are easier to see.

[jbtronics]

I would say Component image generator, seems to fit the overall purpose of this tool quite well.

[jbtronics]

is this PR finished?

[Sebbeben]

Done — renamed to Component image generator everywhere: the tool title, the Tools-menu entry, the route (/tools/component_image_generator), and the permission (@tools.component_image_generator). CI is green.

[Sebbeben]

Rebased onto the latest master. All PHPUnit jobs (PHP 8.2–8.5 × mysql/postgres/sqlite), the asset build and codecov are green.

One heads-up on the red Static analysis: it isn't this PR — the Symfony security-checker step is flagging mcp/sdk v0.7.0 (CVE-2026-53965), a dependency already in master's composer.lock (this PR doesn't touch the composer files), and PHPStan is skipped behind that failing step. It should clear once mcp/sdk is bumped in master — happy to open a separate PR for that if it's useful.