Ben Lesh
Ben Lesh
I think this is a duplicated effort, there's another PR with the same work over here: #105
This is a good idea. The current idiom I think should be nf-bars-stack to mirror nf-area-stack. Requires some thought.
@koryteg it sounds okay to me. The lanes and "frets" were created to precisely match a mockup for the project these components were made for within Netflix. The tricky bit...
Thanks @ratson, I'm looking into it.
@eddieajau as a stop-gap solution couldn't you define your array of routes separately and export them for consumption? ```js var routes = [ /* stuff */]; var router = new...
Related, I think that the current Observable proposal, as it stands could be [simplified quite a bit and I filed an issue there as well](https://github.com/tc39/proposal-observable/issues/201)
I think really I just need to see an open source reference implementation.
My primary concern: I think having a `next` method, and forcing multicast, makes Emitter too high-level and makes the type less useful as a building block. If you remove that...
That's still related to the subscription. Not the emissions. first, take, takeUntil, et al, all cause teardown. Which travels back up the chain. But that's related to the operator chains...
> though that proposal hasn't seen much activity since WHATWG has been adamant that there shouldn't be two native cancellation mechanisms and AbortController already exists. AbortController/AbortSignal looked promising, but RxJS...