You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an onm namespace data model declaration you can currently specify either, a static default value for a property, or programmatically-generate a default value via a callback function. The later case is used in cases like assigning a UUID, or timestamp to a data namespace at construction-time.
It's inconvenient to have to clutter onmd-* modules with additional npm dependencies (e.g. to call node-uuid or onm-bundled util functions). Better to extend the namespace declaration grammar to allow common things like UUID's/timestamps to be declared.
In an onm namespace data model declaration you can currently specify either, a static default value for a property, or programmatically-generate a default value via a callback function. The later case is used in cases like assigning a UUID, or timestamp to a data namespace at construction-time.
It's inconvenient to have to clutter onmd-* modules with additional npm dependencies (e.g. to call node-uuid or onm-bundled util functions). Better to extend the namespace declaration grammar to allow common things like UUID's/timestamps to be declared.
e.g.
The text was updated successfully, but these errors were encountered: