Could we optimize the obj clone?

Check localforage

var t = format(function(str) {
  return str + ''; 
});

should also chain formatters!

var store = new Store({
  title: 'hello',
  items: ['hello', 'world']
})

var items = store.select('items');
items.set(0, 'foo');

select return a datastore from a key.

In the same way we can proxy setters and getters we should be able to proxy the construction of a store.

by default the store data is a type of Object but if you reset the data with an Array it should be an instanceof Array

Alias emitter doesn't work on nodejs

The diff should be in a separate module

guise for format and spread for use

Add array handler and array observer

we should be able to do something like:

store.set({
  key: val
});

it doesn't make a reset but update or add.

we should delete items only if new < old

A plugin to set/get and sync in redis.

may be decompose:

• format
• compute
• pipe

into plugins

the dle function just set as the index as undefined, it doesn't really delete it.

I'm guessing you already peeked at the successor of component: duo. They are directly fetching the project via git-tags. The Problem is that they are prefixed with a "v" and postfixed it with "-alpha". This breaks the whole semver resolution and the installation fails.

node_modules\duo-package\node_modules\semver\semver.js:273
    throw new TypeError('Invalid Version: ' + version);
          ^
TypeError: Invalid Version: v1.2-alpha

Is there a way to work around that or do we need to release versions without any post or prefix?

Thanks

I may be missing the obvious, but how do I get all the data stored in a datastore object as an array? I would like to iterate over the items with forEach, map and so on.

store.change('weight', ...);
store.change('bredele.weight', ...);

Change could accept callback or pipes.

List the differences between a store and a model (more flexilble, etc) and say the reason why it doesn't make sense to use object descriptors with store (because it's not a fixed subset of peroperties).

We should be able to use 'use' on prototype.

Use descriptors for format and compute?

we should test that window exists.

give more details for the events.

store.get('prop.attr');

Listen prop or create new store from it or make diff

store.on('changed prop.attr', ...);

store.set(0,{
  name : 'amy'
});

Would it be nice to update a store array as following:

store.set(0,'name', 'olivier');

Is there a way to optimize it?

component-store instead store-component

To be used in nodejs and brick can use the plugin.

we emit deleted events with index on previous store data.
ex:
old data: 7
new data: 4

deleted events: 5 6 7

Should we emit the actual index?

push, splice, etc

I added an event 'updated' which is trigerred on set, del and reset. You can choose to trigger or not this event by setting the strict mode to true:

//trigger updated
store.set('name','bredele');

//doesn't trigger updated
store.set('name','bredele', true);

It is used internally (by pipe) and is useful for some plugins. For example, the plugin mirror emit an event to the server on changes, and set its data when some data are received from the server.

store.on('updated', function(name, val) {
  socket.emit('change', name, val);
});

socket.on('change', function(name, val){
  store.set(name, val, true);
});

Without the strict node, we will send date in loop to the server (data from server - set local store and trigger change - send data to server on change).

My question is: is there a better way to prevent to send data in loop to the server?

We should initialize the localstore from the constructor.

Pipe with an other store (listen change on one store and set a property in the other)

We could gain about 40% performance.

function Store() {
  Emitter.call(this);
}

Store.prototype = Emitter.prototype;