neo

there can be some mean float value transformations, which result in odd outputs when using the spin down & up buttons.

to resolve this, we are following this strategy (simplified) now:

See: https://github.com/neomjs/neo/issues/4192

{Boolean} submitDateObject
defaults to false

only loop over existing triggers

needs a bit more testing, but looks good so far:

nsWithArrays(names, create, scope) {
    names = Array.isArray(names) ? names : names.split('.');

    return names.reduce((prev, current) => {
        if (create && !prev[current]) {
            if (current.endsWith(']')) {
                return createArrayNs(true, current, prev);
            }

            prev[current] = {};
        }

        if (prev) {
            if (current.endsWith(']')) {
                return createArrayNs(false, current, prev);
            }

            return prev[current];
        }
    }, scope || globalThis);
}

See: https://github.com/neomjs/neo/issues/4151

While the config is implemented on form.field.Base, it can get used on any parent container as an alternative for using dots inside field names.

• form.Container: getValues() => support for arrays
• form.field.Base: support for dots inside field names

• form.Container: getValues() => support for dots inside field names => creating nested objects
• form.field.Text: validOnMount => clean refactoring

• form.field.Text: showOptionalText hotfix. see: https://github.com/neomjs/neo/issues/4123
• more progress on the lazy loaded forms demo app

• core.Base: parseItemConfigs() => smarter support for instance or prototype based configs (inside the hierarchy chain)
• component.Base: render() => deleting the vdom removeDom flag

• Neo.Main.redirectTo() => new remote method for the app worker
• component.Base: hidden hotfix candidate. see: https://github.com/neomjs/neo/issues/4111