fix(ai): correct double-wrap in OCR engine endpoints causing e.map error
CI / CD Pipeline / build (push) Successful in 4m50s
CI / CD Pipeline / deploy (push) Successful in 14m18s

Controller was returning { data: engines } which TransformInterceptor
wrapped again into { data: { data: engines } }. extractData() only peeled
one layer, leaving an object instead of the array — causing .map() to fail
in OcrEngineSelector.

- Return data directly from getOcrEngines() and selectOcrEngine()
- Add Array.isArray guard in OcrEngineSelector as defensive layer
This commit is contained in:
2026-06-02 15:49:39 +07:00
parent e4948ad4c8
commit 754d609399
2 changed files with 5 additions and 10 deletions
@@ -22,7 +22,7 @@ export default function OcrEngineSelector() {
try {
setIsLoading(true);
const data = await adminAiService.getOcrEngines();
setEngines(data);
setEngines(Array.isArray(data) ? data : []);
} catch (_err: unknown) {
toast.error('ไม่สามารถดึงข้อมูล OCR Engines ได้');
} finally {