Nikhil Tilwalli

@staltz, thanks for the response. I'm not clear on the question. Are you wondering why this `domProps` work merits being a part of the driver when I could directly apply...

The term `domProps` was used to indicate that the properties will be applied to the dom element created by this virtual dom node. In `snabbdom` you can do: `input('.some-class', {...

Yeah, that's a good idea, but you seem to imply that it can be accomplished by a `h.ts` fork only. I'm quite new to React, so I may be missing...

Dunno if cypress tests are appropriate but I added one (can remove if there's a leaner way). As of now that test is really wonky. I had to use a...

I integrated your `domPropify` code and added a similar `domHookify` HOC as well. My understanding is: - [x] `style` and `key` should work out of the box, since`snabbdom` and `react`...

I would have no issue making this a separate package, but given the updated modules orientation around the latest implementation (and it's seamlessness with the current approach), I wonder, why...

@staltz I've integrated your feedback. `Modulizer` is a new module/class that layers its functionality on top of `Incorporator`. Modules enablement happens through the new `useModules` function, which (when activated) swaps...

Here's one use case I believe (child state gets added to parent and doesn't get removed). ```javascript const toggle_visibility$ = DOM.select('.foo').events('click').fold((acc, val) => !val, false) const child$ = toggle_visibilty$.map(show =>...

It's not RxJS specific as per https://gitter.im/cyclejs/cyclejs?at=593b5ba06549436c7d32a4ce It doesn't make sense that it would be RxJS specific. The use case is that only one component in a larger application uses...

@kylecordes this is an interesting idea but the structure of this component seems app-specific. Is it true `DOM` sink will be the only non-merged (composed) sink? That may be true...