Support Subschema Validation with boolean logic ("allOf", "oneOf", "anyOf, "not") in conjunction with type validation

[hornworm61]

It appears that something as simple as the following isn't supported:

{
 "$id": "https:/com.foo.test.json",
 "$schema": "http://json-schema.org/draft-07/schema#",
 "definitions": {
   "aType": {
     "$id": "#aType",
     "description": "A Type",
     "type": "object",
     "allOf": [
       {
         "$ref": "#otherType"
       }
     ],
     "properties": {
       "field1": {
         "description": "A field",
         "type": "string"
       }
     }
   },
   "otherType": {
     "$id": "#otherType",
     "description": "Another type",
     "type": "object",
     "properties": {
       "field2": {
         "description": "A field",
         "type": "string"
       }
     }
   }
 }
}

The "allOf" construct in aType is simply dropped when importing this schema, and there is no way to create a schema with this structure in the editor.

A similar problem exists for "oneOf", "anyOf" and "not".

The editor does support a roughly equivalent structure of using a "oneOf" and nesting the object properties below this, but this doesn't help when trying to import existing schemas that already use the simpler approach.