Is enum supported?

[cihad]

Why is the enum not working?

{
  "type": "object",
  "properties": {
    "city": {
      "title": "City",
      "enum": ["Foo", "Bar"],
      "x-jsf-presentation": {
        "inputType": "select"
      },
      "type": "string"
    }
  }
}

but it is ok:

{
  "type": "object",
  "properties": {
    "city": {
      "title": "City",
      "oneOf": [
        { "const": "Foo", "title": "Foo" },
        { "const": "Bar", "title": "Bar" }
      ],
      "x-jsf-presentation": {
        "inputType": "select"
      },
      "type": "string"
    }
  }
}

[ollyd]

Hi @cihad! In your example enum won't work as it would need a corresponding options property within the x-jsf-presentation property. However, whilst this will work it's now deprecated and will be removed in future - our recommended implementation is using oneOf as per your second example.

If you need to use enum in the way you've suggested, whereby the label would also represent the value, contributions to the library are always very welcome!

[cihad]

Enum will always come up. It would be good to support it. Maybe enumLabels can be added to x-jsf-presentation.

[ollyd]

Enum will always come up. It would be good to support it. Maybe enumLabels can be added to x-jsf-presentation.

Hi @cihad agree it would be good to support it. We would suggest enumTitles rather than enumLabels as title is more in line with the json schema spec. If you would like to take a stab at opening a PR, it would be appreciated.

[sandrina-p]

Hi @cihad! Oone more thing we remembered:

Imagine this enum: ["1", 1, true, "true"] Using enumTitles an object, we cannot match the title for each key because they are always strings. So the enumTitles needs to be an array as enum.
In your example, it would be enumTitles: ["Identification", "P45 Document"]

Does this make sense to you?

[cihad]

Yes, it would be better to use enumTitles as an array instead of an object.