after adjusting the "set directly to state" issue #163, we now lose the state. as it turns out, the state had a reference to the parents object (passed as this.props.item) and keeping the reference to that may have been why the state was set in suck a non standard way.
DoD:
items should keep their selected state