matt-esch / virtual-form

Form interface for virtual-dom

virtual-form

Form interface for virtual-dom

WORK IN PROGRESS

The intention is for this to be a set of form node utility functions that will allow us to patch properties to behave how we expect. This is probably better than trying to implement a VNode transform: it's always better to create the thing you wanted in the first place.

This is very early, doesn't work, no tests. I'm working in the open here. However I am closely following the MDN docs and expect to document all of the considered properties.

Form elements

button

fieldset

form

input

keygen

label

legend

meter

optgroup

progress

select

textarea

Contributors

• Matt Esch

MIT Licenced

virtual-form's Issues

Implementing a function?

Hi I'm wondering what the proper way of implementing a virtual-form 'function' would be? Would this work (minus any syntax or logic issues)? Do I have to worry about the parent or children? What about error handling?

module.exports = {
    init: function(vt) {
        this.vt = vt;
        this.name = 'fieldset'
        this.validProps = ['disabled', 'form', 'name'];
    }

    create: function(props, children, opts) {
        props = props || {};

        if (!is_intersection(Object.keys(props), this.validProps)) {
            return undefined;
        }

        return new VNode(
            this.name,
            props,
            childs,
            opts.key || undefined,
            opts.namespace || undefined
        );
    },
    is_intersetion: function(h, a) {
        return a.some(function(e) {
            return h.indexOf(e) >= 0;
        });
    }
}

FAQ: what is the need for this

what problem do you run into doing it naively?