lexfro / slt Goto Github PK

We need a "master" context which will be the context which could be defined as a main user context, associated with current user action. It should be selected automatically (by the first "set" call) and also there should be a way to force it (in case of redirects, for example.) The property of "masterness" will be used to handle conflicts and race conditions: the master context should be the king when in the merge.

If you still interested in achieving Realy-like functionality check this. I highly need help.

We need a way to flush the current Optimistic state to the app.

The main goal of Slots is to provide simplicity and familiarity to isomorphic app development. This is why the default set strategy is gust deep merge. So if we have the request map in the state, and it have, say the body key, if we call Slots.set("request", {url: url}) it will merge the {url: url} into current request map. Sometimes we desire to override this default behavior. This is why we need to provide a way to specify this strategy manually. It will be 2 ways how to do it: you will able to set it in the rules and also it will be possible to specify it directly using third parameter of the set method.

With Slots user is able to set what he want to get it. We need to specify a way to handle events (changes) from outside world (from web socket) and make the state to be consistent with the "World" at any point of time.
We need to support Observables and Generators as well as Promises (implemented) and node-style APIs.

Can you provide an example app? Its no really clear how to use your tool. Suppose TodoApp would be nice.