Boolean "required" field on object property leads to serialization failure

I need to interact with an API specified using JSON Schema draft-03. cargo-typify errors during serialization of that API. The issue is the required: [bool] notation used on object properties in pre draft-04 versions of JSON Schema. The following is a minimal example where the serialization fails:

{
  "$schema": "http://json-schema.org/draft-03/schema#",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "required": true
    }
  }
}

This happens because schemars defines the required field as following:

pub struct RootSchema {
    //...
    #[serde(flatten)]
    pub schema: SchemaObject,
    //...
}
pub struct SchemaObject {
    //...
    #[serde(flatten, deserialize_with = "skip_if_default")]
    pub object: Option<Box<ObjectValidation>>,
    //...
}
pub struct ObjectValidation {
    //...
    pub required: Set<String>,
    //...
}

Since required have a wrong type, serde-json fails trying to deserializing the above example to an ObjectValidation.

To fix it for our use, I implemented parse-jsonschema to seperate the structure parsed into from the internal representation used, and correctly transforms the old required structure to the new.

I have used this in cargo-typify in our fork of typify (found here).

If you are interested in supporting the old required syntax in typify, I am ready to put in some time to make it ready for upstreaming, otherwise, feel free to close this issue.

Some notes on our current implementation:

I choose to create a separate structure from the one in schemars, since the structure in schemars seems to mainly be used for generating JSON Schema. It would be less fit for that purpose if it was modified to support serialization from any JSON Schema found in the wild.

The current implementation does not take the specified version of the JSON Schema into account. I have not checked the current specification to see if it disallows required fields in different contexts than the use in object schemas.

In our fork of typify the only crate which currently works is cargo-typify. I have not looked into why.

oxidecomputer / typify

Boolean "required" field on object property leads to serialization failure #552