Rationale Behind Including Titles and Descriptions in JSON Schema Definitions
What's the rationale for representing
as opposed to just:
Those title & descriptions objectively don't add any additional information/value, rather they just add clutter/verbosity to the generated JSON Schema
S.String, S.Number, S.Boolean etc as:as opposed to just:
Those title & descriptions objectively don't add any additional information/value, rather they just add clutter/verbosity to the generated JSON Schema
