Recycle
Convert functional/reactive object description into React component.
You don't need another UI framework if you want to use RxJS.
Installation
npm install --save recycle
Example
const Timer = recycle({
initialState: {
secondsElapsed: 0,
counter: 0
},
update(sources) {
return [
sources.select('button')
.addListener('onClick')
.reducer(function (state) {
state.counter = state.counter + 1
return state
}),
Rx.Observable.interval(1000)
.reducer(function (state) {
state.secondsElapsed = state.secondsElapsed + 1
return state
})
]
},
view(props, state) {
return (
<div>
<div>Seconds Elapsed: {state.secondsElapsed}</div>
<div>Times Clicked: {state.counter}</div>
<button>Click Me</button>
</div>
)
}
})
You can also listen on child component events and define custom event handlers. Just make sure you specify what should be returned:
import CustomButton from './CustomButton'
const Timer = recycle({
initialState: {
counter: 0
},
update(sources) {
return [
sources.select(CustomButton)
.addListener('customOnClick')
.reducer(function (state, returnedValue) {
state.counter = state.counter + returnedValue
return state
})
]
},
view(props, state) {
return (
<div>
<div>Times Clicked: {state.counter}</div>
<CustomButton customOnClick={e => e.something}>Click Me</CustomButton>
</div>
)
}
})
Replacing Redux Connect
If you are using Redux,
Recycle component can also be used as a container (an alternative to Redux connect
).
Advantage of this approach is that you have full controll over component rerendering (components will not be forceUpdated "from the outside").
Also, you can listen for a specific part of the state and update your component only if the state is changed.
export default recycle({
dispatch (sources) {
return [
sources.select('div')
.addListener('onClick')
.mapTo({ type: 'ADD_TODO', text: 'hello from recycle' })
]
},
update (sources) {
return [
sources.store
.reducer(function (state, store) {
return store
})
/**
* Example of Subscription on a specifing store property
* with distinctUntilChanged() Component will be updated only when property is changed
*
* sources.store
* .map(s => s.specificProperty)
* .distinctUntilChanged()
* .reducer(function (state, specificProperty) {
* state.something = specificProperty
* return state
* })
*/
]
},
view (props, state) {
return <div>Number of todos: {store.todos.length}</div>
}
})
API
Component description object accepts following properties:
{
propTypes: { name: PropTypes.string },
displayName: 'ComponentName',
initialState: {},
dispatch: function(sources) { return Observable },
update: function(sources) { return Observable },
view: function(props, state) { return JSX }
}
In update
and dispatch
functions, you can use the following sources:
/**
* sources.select
*
* select node by tag name or child component
*/
sources.select('tag')
.addListener('event')
sources.select(ChildComponent)
.addListener('event')
/**
* sources.selectClass
*
* select node by class name
*/
sources.selectClass('classname')
.addListener('event')
/**
* sources.selectId
*
* select node by its id
*/
sources.selectId('node-id')
.addListener('event')
/**
* sources.store
*
* If you are using redux (component is inside Provider)
* sources.store will emit its state changes
*/
sources.store
.reducer(...)
/**
* sources.state
*
* Stream of current local component state
*/
sources.select('input')
.addListener('onKeyPress')
.filter(e => e.key === 'Enter')
.withLatestFrom(sources.state)
.map(([e, state]) => state.newItemInput)
.map(addRepoInputSubmitted)
/**
* sources.props
*
* Stream of current local component props
*/
sources.select('input')
.addListener('onKeyPress')
.filter(e => e.key === 'Enter')
.withLatestFrom(sources.props)
.map(([e, props]) => props.newItemInput)
.map(addRepoInputSubmitted)
FAQ
Why would I use it?
- Greater separation of concerns between component presentation and component logic
- You don't need classes so each part of a component can be defined and tested separately.
- Component description is more consistent.
There is no custom
handleClick
events orthis.setState
statements that you need to worry about. - State is calculated the same way as for redux store:
state = reducer(state, action)
. - Redux container looks like a normal component and it's more clear what it does.
- Easy to use in an existing React application (choose components which you wish to convert).
Why would I NOT use it?
- Observables is not your thing.
- You need more controll over component lifecycle (
shouldComponentUpdate
,componentDidMount
)
What is this? jQuery?
No.
Although it resembles query selectors, Recycle uses React’s inline event handlers and doesn’t rely on the DOM. Since selection is isolated per component, no child nodes can ever be accessed.
Can I use CSS selectors?
No.
Since Recycle doesn't query over your nodes, selectors like div .class
will not work.
How does it then find selected nodes?
It works by monkeypatching React.createElement
.
Before component is rendered, for each element,
if a select query is matched, recycle sets inline event listener.
Each time event handler dispatches an event,
it calls selectedNode.rxSubject.next(e)
Can I use it with React Native?
Yes.
Recycle creates classical React component which can be safely used in React Native.
Previous Version
Recycle v2.0 is much smaller library from its predecessor. It is focussed only on making React components use RxJS for defining component state and handling events.
If you are interested in previous version, check here