Thanks for your continued great work on this! I've got another feature request!

It appears as if objects in content types aren't handled properly in the UI. As you can see here, the UI is asking me to "Enter crafting…" with a freeform text field, and then the individual properties below it.

The JSON schema for this field is what I'd expect:

"crafting": {
  "type": "object",
  "properties": {
    "textile": {
      "type": "number"
    },
    "wood": {
      "type": "number"
    },
    "metal": {
      "type": "number"
    },
    "stone": {
      "type": "number"
    },
    "elementalis": {
      "type": "number"
    },
    "mithril": {
      "type": "number"
    },
    "fadeite": {
      "type": "number"
    }
  },
  "required": [
    "textile",
    "wood",
    "metal",
    "stone",
    "elementalis",
    "mithril",
    "fadeite"
  ],
  "additionalProperties": false
},

This makes complex content types difficult to work with. What I'd love to see is objects transformed into fieldsets with their field name as their legend. That would both logically group the fields underneath it, which is the intent of having them as an object to begin with, and remove the confusing input for an object type.

(I also notice that the order of the fields inside objects is not preserved, that feels like a potentially related bug)