When using data generated by a schema containing anyof, the result is incorrect after assignment to the editor.

Expected behavior

The editor can correctly assign values based on json

Actual behavior

The editor cannot use the correct anyOf subkey when assigning the anyOf field

Steps to reproduce the behavior

schema

{
  "title": "anyof badcase",
  "type": "object",
  "properties": {
    "items": {
      "title": "title",
      "type": "array",
      "format": "tabs",
      "items": {
        "title": "item",
        "headerTemplate": "{{self.handler}}",
        "options": {
          "keep_oneof_values": false
        },
        "anyOf": [
          {
            "title": "item a",
            "properties": {
              "handler": {
                "default": "aaa"
              },
              "___a": {
                "title": "___",
                "type": "string"
              }
            }
          },
          {
            "title": "item b",
            "properties": {
              "handler": {
                "default": "bbb"
              },
              "___b": {
                "title": "___",
                "type": "string"
              }
            }
          },
          {
            "title": "item c",
            "properties": {
              "params": {
                "properties": {
                  "items": {
                    "title": "sub items",
                    "type": "array",
                    "format": "tabs",
                    "items": {
                      "options": {
                        "keep_oneof_values": false
                      },
                      "title": "sub item",
                      "headerTemplate": "{{self.handler}}",
                      "anyOf": [
                        {
                          "title": "item a",
                          "properties": {
                            "handler": {
                              "default": "aaa"
                            },
                            "___a": {
                              "title": "___",
                              "type": "string"
                            }
                          }
                        },
                        {
                          "title": "item b",
                          "properties": {
                            "handler": {
                              "default": "bbb"
                            },
                            "___b": {
                              "title": "___",
                              "type": "string"
                            }
                          }
                        }
                      ]
                    }
                  }
                }
              },
              "handler": {
                "default": "ccc"
              },
              "___c": {
                "title": "___",
                "type": "string"
              }
            }
          }
        ]
      }
    }
  }
}

generated data:

{
  "items": [
    {
      "handler": "aaa",
      "___a": ""
    },
    {
      "handler": "bbb",
      "___b": ""
    },
    {
      "params": {
        "items": [
          {
            "handler": "aaa",
            "___a": ""
          },
          {
            "handler": "bbb",
            "___b": ""
          },
          {
            "handler": "aaa",
            "___a": ""
          }
        ]
      },
      "handler": "ccc",
      "___c": ""
    }
  ]
}

Update the editor with the generated data.

screenshot

[drzax]

Sorry, I don’t have time for that and the bug is already explained quite well here. I just wanted to point out that this is still a bug, and rather an annoying one which is difficult to track down. Feel free to use/manage this bug report however you think is appropriate.

On Mon, 18 Feb 2019 at 06:17, Peter Klein [e-mail] wrote:

@drzax https://github.com/drzax I suggest you open a new issue with specific examples etc. As it looks like the the original reporters is no longer around.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/json-editor/json-editor/issues/128#issuecomment-464503725, or mute the thread https://github.com/notifications/unsubscribe-auth/AAkaUx5iEv59X8SXUflLedOwHQwjwivGks5vObj1gaJpZM4VFM44 .

[drzax]

In my opinion this ticket should not have been closed. As far as I can tell, there is still no foolproof way to ensure that the correct schema is used for children in a oneOf or anyOf when loading data.

The comment suggesting this has been fixed uses data that makes it appear to work, but as @wclssdn commented earlier it still doesn’t work if the sub-items are more complex and the data (although unambiguously matching a specific schema) is incomplete.

To test this, load up the schema link posted by @pmk65 in the comment declaring this fixed, but then refresh the form using data from @Richacinas comment and you will see that the third item (ccc) now incorrectly uses the aaa schema.