Surfaced during openapi-numeric-schema-truth (Web #222). The generated OpenAPI schema for the topic-trends response diverges from the Web consumer's hand-written shape:
- generated renames the array field
topics → trends
- generated drops the
from / to range fields
Web keeps TopicTrendsResponse hand-written because a swap would break the hook's public shape. Reconcile the Platform DTO/serialization so the emitted schema matches the intended wire contract, then Web can adopt the generated type.
Ref: Web use-analytics.ts, spec openapi-generated-types.
Surfaced during openapi-numeric-schema-truth (Web #222). The generated OpenAPI schema for the topic-trends response diverges from the Web consumer's hand-written shape:
topics→trendsfrom/torange fieldsWeb keeps
TopicTrendsResponsehand-written because a swap would break the hook's public shape. Reconcile the Platform DTO/serialization so the emitted schema matches the intended wire contract, then Web can adopt the generated type.Ref: Web
use-analytics.ts, specopenapi-generated-types.