18 lines
848 B
Markdown
18 lines
848 B
Markdown
|
---
|
||
|
|
id: 18
|
||
|
|
title: Introduce ZAPHandler interface for getContent()
|
||
|
|
status: done
|
||
|
|
priority: medium
|
||
|
|
created: 2026-07-17T03:57:59.054256365+02:00
|
||
|
|
updated: 2026-07-18T11:51:03.280085523+02:00
|
||
|
|
started: 2026-07-18T11:51:03.281402582+02:00
|
||
|
|
completed: 2026-07-18T11:51:03.281402582+02:00
|
||
|
|
tags:
|
||
|
|
- framework
|
||
|
|
class: standard
|
||
|
|
---
|
||
|
|
|
||
|
|
From framework review (docs/framework_review.md), P1-7. Currently getContent() is convention-only — no interface enforces it. A handler missing the method fails at runtime, not definition time. Fix: create a ZAPHandler (or ModeHandler) interface with public function getContent(), implement it on all existing handlers, add instanceof check in ZAPController.
|
||
|
|
|
||
|
|
[[2026-07-18]] Sat 11:50
|
||
|
|
Created ZAPHandler interface with getContent(), implemented on ZAPHome/ZAPDisplay/ZAPZap, added instanceof check in ZAPController::fetch().
|