additionalProperties form - enum for key

Prerequisites

• I have read the documentation;

Description

Would it be possible to add a feature that would enable the user to set a given set of all possible keys of additionalProperties?

At the moment, I validate the keys with propertyNames which works, but it would be much cleaner for the user to have it set as an enum.

Expected behavior

additionalProperties are rendered with a dropdown key selection if enum given.

Actual behavior

additionalProperties have to options for key customizations and propertyNames are ignored in the rendering phase (but used for validation).

Version

Latest.

[bmschmidt]

Not the OP, but as it happened was just googling for almost this same issue. My expected behavior was that, when there is a constraint on property names, the interface elements will use dropdowns for the keys to any additionalProperties.

For example, in the following schema, when you add another property to the array with a plus button, the values of the properties give you a dropdown to choose from “val1” and “val2”, but you just get a text field to write into without any hints about permitted values are. Instead, it should be a dropdown to choose from ‘foo’ or ‘bar.’

{
  "type": "object",
  "propertyNames": {
    "enum": [
      "foo",
      "bar"
    ],
    "type": "string"
  },
  "additionalProperties": {
    "type": "string",
    "enum": [
      "val1",
      "val2"
    ]
  }
}

Great library, thanks for your work.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please leave a comment if this is still an issue for you. Thank you.