where's the View obv?

README:

The trick is that each view exposes an observable that represents it’s current state. An observable is like an event meets a value. it’s an changing value that you can observe. Events, promises, or streams are similar, but not quite the right choice here.

I was promised an observeable. I can’t see how to access it (code nor docs) EITHER - provide db[viewName].obs OR - can we clarify what is meant by that paragraph 😃

[mixmix]

I imagined I would be intersted in using the obv of the viewState … the sequence as an obv doesn’t seem useful? If it isn’t that useful I would EITHER remove the talk about obv being exposed (which sent me looking), OR mention the obv that’s in there (value) as part of the api

I’m aware I’m poking the READMEs without having built a lot of things with this stuff yet. I am doing this because I want others to find it clear where I have not. For the most part it’s been pretty clear, but figure we should do this now, because coming back to it and seeing things fresh is hard. Trust you’ll tell me if I’m off with my feel for the use of things.

On Wed, 10 Jan 2018 at 17:43 Dominic Tarr [e-mail] wrote:

Oh no, it’s [viewName].since the log also has a since… since being the sequence number of the latest message processed. [viewName].value is a flumeview-reduce feature. flumeview-level doesn’t have that.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/flumedb/flumedb/issues/15#issuecomment-356498283, or mute the thread https://github.com/notifications/unsubscribe-auth/ACitntnytnZhVbC1oh2mnBjPYO0nI13mks5tJD_kgaJpZM4RYbcU .

[christianbundy]

I think this is resolved and ready to close, please re-open if not!