Right now it doesn't allow us any kind of options, since it's an array:

someArray: [
   {
        ...
   }
]

Currently the best idea I have is to have something like:

someArray: {
    type: "array",
    item: {
       /* item schema */
    }
}

@silviubogan Any better ideas?

Relevant places in code: here and here.

The currently unsupported input types from the ones enumerated here are:

• color
• datetime
• datetime-local
• email
• file
• hidden
• month
• password
• radio
• range
• tel
• time
• url
• week

I left out search and others because I think they do not fit in a form created with this module.

When setting editable: true to an object containing fields (I tried name), the editing process it buggy.

@IonicaBizau, when this issue will be critical from your point of view, please tell me what unit testing library I should use, because I know that you worked with these. I never did unit tests before but I think it would be useful.

Like #5 but for removing items. ❇️

For example:

false
true

Instead of:

false
true
false
false

Not sure when this should be checked, probably in the add possible values form. If the developer passes possible: [false, false, true] we will just render it that way.

Any ideas?

The default value of the <select>s, in the fields with multiple possible values, in tables' footer row with the new item controls, is an empty string set here but because of a Chromium bug, the default selected value is not an empty string but the text of the first option in the <select>.

See:

• a StackOverflow question I asked: http://stackoverflow.com/q/33076851/258462 ;
• the Chromium issue I opened: https://code.google.com/p/chromium/issues/detail?id=542134 .

This seems to be already implemented here but I must test it.

This should add support for representations of arrays other than tables (for example, a tag list like the tags of a question on StackOverflow when editing a question).

Looks like a very cool project!

I think having an example of how the plugin is implemented in README.md or a static hosted demo where someone can view the source would go a really long way. Even after reading the docs I am unsure how to use the plugin, and I am not a js newb. I would be happy to open up a PR if you guys provide some guidance on how the plugin is implemented.

If possible, instead of outputting this string:

"born": "1995-09-14T00:00:00.000Z"

output the following

"born": new Date(1995, 8, 14)

Like in objects (#26), by specifying editableFields: true in the definition of the array or editable: true in the definition of individual fields in an array.

Maybe with a schema property editableFields. Related to #7 and #9.

Like #7 but for deleting fields–there should be a field like removeField or something... 😄

Related to #22 and #9. Maybe this functionality should be enabled when the schema of an object contains reorderableFields: true.

• require("jxutils")
• require("ul").deepMerge
• require("typpy")
• for iterating objects: require("iterate-object")–could be useful for arrays too

To bundle everything up, use browserify. The priority of this issue increases as the module grows... 🚀

Currently, there is a lot of spaghetti code that makes solving bugs and extending the plugin very hard. I started working on this and I am working very hard to finish this as soon as possible.

The JS code related to the field editor should be very flexible, maybe customizable.

This means that when a field of an elementary type is added inside an object inside the parent object in a cell under a column of type "object", that field should be added in all the cells under that column of type "object".

Related to #34.

Make it possible to reorder elements in arrays.

I suggest adding a new <td> next to the delete button in items, a <td> which will be a drag handler containing three horizontal lines. Or maybe would it be better if each item would have two buttons with up and down arrows?

This variable specifies the property in the schemas which contains an array of names of fields under that schema. By default it is _order.

Not yet implemented...