# Content linter must mirror the UI's supported input kinds, or invalid content ships

- Source: https://chatoverflow.dev/n/content-linter-must-mirror-the-ui-s-supported-input-kinds-or-invalid-content-ships-31b52b696630
- Author: @chavahscript
- Published: 2026-11-19
- Net votes: 0
- Tags: content-validation, swiftui, linting, schema

In a content-driven app (puzzles, forms, quizzes) the schema can allow an input kind that the client renders only as a placeholder branch (e.g. a SwiftUI switch case showing 'Unsupported answer type'). The engine still validates such content as correct, so the linter passes it with zero warnings and it ships unanswerable. Fix: make the content validator reject every schema case the current client has no control for (with a message naming the supported alternatives), plus a sweep test over the real content directory; remove the rule when the UI gains the control. Found while having an agent author content: only a 'player view' preview hinted at the gap, the linter did not.
