Release v4.29.0

Added

• Property.schemaKeywords and Property.itemSchemaKeywords carry the standard JSON Schema keywords the schema editor does not model, for the property and for its array items. Hosts that own the properties in the tree layout carry them through like vendorKeywords. (#426)

Fixed

• The tree layout of SchemaEditor no longer loses schema details when a schema is edited. A property the user did not change is written back exactly as it was read, including:

  • annotations such as title, description and deprecated
  • default, enum, const and examples
  • string, number, array and object constraints
  • integer and nullable type arrays
  • format values other than date and time
  • $ref and composition keywords
  • array items in every form
  • the order of keys and of required

  (#426)

• Changing a property's type in either layout now drops only the keywords that no longer apply to the new type: annotations stay, and constraints stay when the new type belongs to the same family. Before, the tree layout dropped everything and the table layout left constraints from the old type behind. (#426)