neo

see: https://github.com/neomjs/neo/issues/2669

1-liner release.

the new generic logic was checking the key instead of the value for sub-level entries.

This did affect the docs app. Fixed now.

The new ColorField is highly configurable. We can e.g. display non color related names and show different colors for each theme.

https://www.youtube.com/watch?v=uf_RlZ9fHwM

There are several enhancements on form.field.Select as well, e.g. a forceSelection config which will onFocusLeave() set the value to the hintRecordId (typeAhead suggestion), in case there is no selection.

Rendering the initial value requires to use the innerHTML instead of using the value attribute (this one only works for dynamic changes).

I added bottom borders for textarea triggers and set the resizable config to false per default.

This release also includes changes on form.field.Select:

Per default, the field will try to store a recordId (keyProperty) inside the value config, in case the text input matches a record displayField exactly. The change event will now pass record ids if possible.

A new forceSelection config is in place, which will limit change events to valid entries.

You can now use the optional main thread addon: main.addon.Cookie

to get read & write access for document.cookie from within the app worker.

The SCSS builds not use the sass:math lib for src and theme folders, which resolve the SASS v2 build warnings.

The file counters got adjusted to show numbers for each environment (development, production).

The theme-map.json files will now also get saved into the dist folder.

The App worker will now fetch these fail according to the current env.

The build-all script should now run without any warnings.

Neo.config.useDomIds default value true.

Setting the new config to false will store vdom based ids inside a data-neo-id DOM element property rather than using the real dom id.

Expanding the settings view inside the calendar was broken due to removing the MainContainer ntype, which is actively in use inside component queries. fixed now.

The calendar now has an "Add Calendar" button at the bottom left, which adds new items into the list.

You can customise them with the edit form.

core.Base now allows to change the id config at run time. This can be helpful for e.g. Lists which contain component based items, in case we want to re-use the instances.

In case we change an id, the entries inside manager.Instance as well as manager.Component will get adjusted.

Be aware that component ids will get mapped to DOM ids, so they have to stay unique.

=> only use this feature in case you are 100% sure what you are doing. Neo will log errors in case duplicate ids occur.

The event related drag & drop logic got moved into calendar.view.week.plugin.DragDrop and will only get lazy loaded if needed.

we can now update fields without firing the recordChange event.

button.Base: added a type="button" dom attribute to prevent the browser from assuming they are submit buttons.

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

https://youtu.be/JAct-p40hbI

this release also includes a code cleanup on several files.

We can now use record.set() to bulk update multiple record fields at once.
This will result in one combined recordChangeevent.

The signature of the event got adjusted, containing a fields object (name, oldValue, value).

data.RecordFactory.isRecord() got adjusted to honor dist/prod (minified class names).

The calendar month and week views now listen to calendar and event store recordChange events to update the view if mounted. In case a view is not mounted (inactive card / tab), the changes will get pushed to the virtual dom engine after a re-mount.

https://github.com/neomjs/neo/blob/dev/examples/calendar/weekview/MainContainer.mjs

leaving the menu tree will now hide (unmount) it.