APISIX

APISIX plugins ship JSON Schema definitions for their configuration. If APISIX Dashboard can render plugin configuration forms directly from JSON Schema, developer experience improves significantly and reduces manual UI maintenance. Goals (Deliverables) Must-have: A reusable SchemaForm (or equivalent) that renders basic types: string/number/integer/boolean/object/array. enum support (Select/Radio etc), defaults, required fields, basic constraints (min/max, pattern, etc) where feasible. Support at least the key complex patterns used by APISIX plugin schemas: oneOf (select one option and render corresponding fields) dependencies / conditional fields (Stretch) anyOf if present in target schemas Validation pipeline: validate form values against schema (AJV) and show errors in UI consistently. Documentation + developer guide: how to add/extend schema-to-widget mapping. Tests (unit + minimal integration) to prevent regressions for schema parsing and conditional rendering.