Jeppe B 7174e3be6c fix(api): coerce string booleans before persisting module_config bool values (#359) ...

PHP truthy semantics treat the literal `'false'` as truthy, so `$value ? 'true' : 'false'` in `setVariableValue()` persisted every 'switch off' request as `'true'` for ~30 modules with bool config variables. Canonicalise via the existing `inputToBool()` helper before the ternary so JSON.stringify(boolean) inputs land on the right storage string.

Live repro (api-v2.truckwash.io, 2026-08-10 09:25):
```
POST /minimax/config {variable:"enabled", value:"false"} → 200
GET  /minimax/config?variable=enabled → {value:true, ...}      ← unchanged
POST /minimax/config {variable:"enabled", value:false}   → 200
GET  /minimax/config?variable=enabled → {value:false, ...}     ← JSON bool works
```

Tests: `tests/Unit/MiniMax/MiniMaxEnabledSetVariableValueTest.php` (6 assertions, captures the UPDATE column value via stubbed `updateVariableValue`/`insertVariableValue` for string/boolean × true/false × insert/update paths).

Companion pleno-vue PR #281 lands the matching UI-side fix (`onMiniMaxEnabledSwitch` re-fetches + optimistic rollback).

2026-08-10 09:21:56 +02:00

..

MiniMaxConfigSecretRedactionTest.php

test(api): lock MiniMax config redaction + isSet contract (#358)

2026-08-10 08:45:10 +02:00

MiniMaxEnabledSetVariableValueTest.php

fix(api): coerce string booleans before persisting module_config bool values (#359)

2026-08-10 09:21:56 +02:00