Inputs missing in form when using 'startval'

[SebT]

When I generate a form with no 'startval' property it works perfectly, all properties specified in the schema can be set via the form.

But if I want to edit an existing object (by using 'startval''), the properties of the schema that are not defined for the existing object don't generate inputs.

For instance if I have this schema:

{
  type: "object",
  properties: {
    test1: {type: "string"},
    test2: {type: "string"},
    test3: {type: "string"}
  }
}

And I generate a form with startval equal to {test2: "testing"} there is no input for 'test1' and 'test3', I can only edit 'test2'.

How to fix this please?

EDIT: I went through the source code and found this object editor's setValue function:

// First, set the values for all of the defined properties
    $each(this.editors, function(i,editor) {      
      if(typeof value[i] !== "undefined") {
        // If property is removed, add property
        if(editor.property_removed) {
          self.addObjectProperty(i);
        }

        editor.setValue(value[i],initial);
      }
      else {
        // If property isn't required, remove property
        if(!initial && !editor.property_removed && !editor.isRequired()) {
          self.removeObjectProperty(i);
          return;
        }

        editor.setValue(editor.getDefault(),initial);
      }
    });

self.removeObjectProperty(i); is the problem here. Can you please add an option to disable this and don't remove editors for which the 'startvat' object has no value?

[jdorn]

There currently isn't a way to do exactly what you want. If you want those properties to always be there, you can either mark them as required in the schema or set the required_by_defaullt option.

I'd like to add more fine-grained control over when properties are removed, but it gets fairly complicated, especially when trying to maintain backwards compatibility.

Using required in the schema:

{
  "type": "object",
  "properties": {
    "test1": {"type": "string"},
    "test2": {"type": "string"},
    "test3": {"type": "string"}
  },
  "required": ["test1","test2","test3"]
}

Using the required_by_default option:

// Globally
JSONEditor.defaults.options.required_by_default = true;

// Per-instance
var editor = new JSONEditor(element, {
  schema: schema,
  required_by_default: true
});

[SebT]

The thing is that those properties are not supposed to be required. The user can decide not to provide values for these properties.
And if I declare them to be so, it'll cause problems because the schema is not used exclusively with json-editor.

I think the best solution is to pass an option to the schema or the jsoneditor constructor that disables property removing