Idea for window/document listeners, and possibly context/state #408

ashaffer · 2016-02-19T19:38:57Z

I was thinking about binding listeners to window/document/body, which right now kind of sucks. You have to wire that up outside of your component system, track the handler yourself, remove it when you're destroyed, etc. It's a hassle, and as far as I can tell, there's no reason we can't just re-use the normal declarative syntax for these as well, by leveraging special components, e.g.:

import {Body} from 'deku'

function Dropdown () {
  return (
    <Body onClick={close}>
      <div>{children}</div>
    </Body>
  )
}

Similarly with other types of events. popstate, resize, etc. I've implemented these ideas in vdux like this for an idea of how this could work. This cleans up code that needs to do these things enormously, and maybe most importantly decouples them from effect management systems, which makes components more portable and reusable. Not to mention that it just generally limits the number of abstractions to be learned and considered.

I think you can also use this pattern for other types of effectful things, like context/state (similarly to react-redux's Provide component).

Thoughts?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Idea for window/document listeners, and possibly context/state #408

Idea for window/document listeners, and possibly context/state #408

ashaffer commented Feb 19, 2016

Idea for window/document listeners, and possibly context/state #408

Idea for window/document listeners, and possibly context/state #408

Comments

ashaffer commented Feb 19, 2016