react-packet
v0.0.1
Published
React Packet is an alternative interface to `react-redux` that helps you hide the internal complexity of action creators and selectors from your components and encapsulates that logic in topic-based files. Packet helps you to think in terms of `Users`, `P
Downloads
2
Readme
React Packet
React Packet is an alternative interface to react-redux
that helps you hide the internal complexity of action creators and selectors from your components and encapsulates that logic in topic-based files.
Packet helps you to think in terms of Users
, Projects
, Groups
, OtherBusinessObjects
instead of separating out selectors
, action creators
, and reducers
.
Instead of this in your components:
import { connect } from 'react-redux';
import usersForGroupSelector from './selectors';
import loadUsersForGroup from './action-creators';
const mapStateToProps = (state, props) => {
return {
users: usersForGroupSelector(state, props.groupId)
};
};
const mapDispatchToProps = (dispatch, props) => {
return {
loadUsers: () => loadUsersForGroup(props.groupId)
};
};
export default connect(mapStateToProps, mapDispatchToProps)(UserList);
Write this:
import { consume } from 'react-packet';
import users from './user-packet';
export default consume(users.forGroup(props => props.groupId))(UserList);
Installation
If you already have react-redux
and redux
in your project, run
npm install --save react-packet
Otherwise,
npm install --save redux react-redux react-packet
Quick Start
Create packets of state that can be used across your app:
// import packAll where you deal with Redux state, to create a nice consumable packet of state and actions
import { packAll } from 'react-packet';
const users = packAll({
// Each property you pass to packAll becomes a function that can be called to consume a packet.
// any selector functions or values passed to `forGroup()` will become parameters to the selector and actions functions
// E.g. we could call `users.forGroup(props => props.groupId)` to grab a groupId from the component props or `users.forGroup(4)`
// to pass a constant value through
forGroup: {
// selector will be called as part of mapStateToProps and can return any useful props when thinking about "users for a group".
// A nice option is to use Reselect's createStructuredSelector here
selector: (state, groupId) => {
return {
users: state.groups[groupId].users,
//... anything else someone might want for working with users
};
},
// actions will be called as part of mapDispatchToProps and should return functions that dispatch actions.
// if you don't need any context like groupId, you can use a plain object here and each function property will be converted to a dispatcher
// just like with connect()
actions: (dispatch, groupId) => {
return {
loadUsers: () => dispatch({
type: 'loadUsersForGroup',
groupId: groupId
})
};
};
};
});
Then consume them in React components:
// import consume where you create a Redux-connected React.Component
import { consume } from 'react-packet';
// a stateless component that might want some user info
const UserList = ({ users, loadUsers }) => (
<ul>{users.map(user => <li {...user} />)}</ul>
<button onClick={loadUsers}>Load</button>
);
// grab the packets you want for your current context and pass them to consume() to create a higher-order component.
const withUsersForGroup = consume(users.forGroup(props => props.groupId));
const GroupUserList = withUsersForGroup(UserList);
ReactDOM.render(
<Provider store={createStore(...)}>
<GroupUserList groupId={7} />
</Provider>)
API Reference
pack(packetDescription : PacketDescription) : PacketMaker
Given a packetDescription
return a generated Packet
function.
PacketDescription { selector: Selector|()=>Selector, actions: Actions:{}}
Selector (state[, props]) => stateProps
Actions (dispatch[, props]) => dispatchProps
PacketMaker (...contextSelectors) => Packet
Packet { mapStateToProps, mapDispatchToProps, minimumSelectorsExpected?: number }
packAll(packetDescriptionMap : PacketDescriptionMap) : { [key: string]: PacketMaker }
Given an object where each property is a packetDescription
, return a new object with the same property names whose values are the generated Packet
s.
PacketDescriptionMap { [key: string]: PacketDescription }
consume(packets[, mapPacketsToProps[, mergeProps[, connectOptions]]]) : Component => ConnectedComponent
packets Array|Packet
mapPacketsToProps(...packetProps) (...Array<{}>) => {}
Takes in the stash and dispatch props from each packet as a separate argument and combines all properties into one object. For example,
it might be called like mapPacketsToProps({ users, loadUsers }, { projects, loadProjects })
. By default each arguments will be combined into
a single object with Object.assign
.
mergeProps(allPacketProps, ownProps) ()
Combine the packed properties with any properties passed in from the parent. Be default this will use Object.assign({}, ownProps, allPacketProps)
.
Longer Example
Redux states are generally normalized so that details about an entity can be shared and updated as new data comes in. That means when thinking about users, groups, projects, andt he relationships between them, you might have state like this:
{
"users": {
"userA": {"some":"details"},
"userB": {"some":"details"}
},
"groups": {
"groupA": {"some":"details"},
"groupB": {"some":"details"}
},
"projects": {
"projectA": {"some":"details"},
"projectB": {"some":"details"}
},
"usersByGroup": {
"groupA": {
"isLoading": false,
"hasAllLoaded": false,
"nextPage": 2,
"errors": [],
"users": ["userA", "userB"]
},
"groupB": {
"isLoading": true,
"hasAllLoaded": false,
"nextPage": 2,
"errors": [],
"users": []
}
},
"usersByProject": {
"projectA": {
"isLoading": false,
"hasAllLoaded": false,
"nextPage": 2,
"errors": [],
"users": ["userB", "userC"]
},
"projectB": {
"isLoading": true,
"hasAllLoaded": false,
"nextPage": 2,
"errors": [],
"users": []
}
},
}
But when working with this state in your code, you typically don't want to deal with all that normalized state and understanding how it fits together. Ideally you'd handle that all in one place and expose it in a more intuitive shape. This is where React Packet comes in. It encourages you to create that "one place".
pack()
pack()
is how you create that place. pack
lets you define selectors and action creators that take in any context from the caller, and output the appropriate props and actionCreators. Below you'll see a users.forGroup(props => props.groupId)
packet and a users.forProject(props => props.projectId)
packet. Each has a selector
and an actions
property that deliver tailored data about users.
// state/users.js
import { pack } from 'react-packet';
export default pack({
forGroup: {
selector: (state, groupId) => {
// ...combine all the various bits of state...
const usersForGroup = state.usersByGroup[groupId];
return {
...usersForGroup,
users: usersForGroup.users.map(userId => state.users[userId]),
};
// returns {
// users,
// isLoading,
// hasAllLoaded,
// errors
// }
},
actions: (dispatch, groupId) => ({
loadUsers: () => dispatch({ type: 'LOAD_USERS', groupId })
})
},
forProject: {
selector: (state, projectId, filterTerm) => {
// ...combine all the various bits of state...
const usersForProject = state.usersByProject[projectId];
return {
users: users.filter(user => user.name.indexOf(filterTerm) !== -1,
isLoading: usersForProject.isLoading,
hasAllLoaded: usersForProject.hasAllLoaded,
errors: usersForProject.errors
};
},
actions: (dispatch, projectId, filterTerm) => ({
loadUsers: () => dispatch({ type: 'LOAD_USERS', projectId })
})
},
});
consume()
consume()
is how you consume a packet. You call it with your packets, passing in any required context parameters. It's a higher-order component that will call connect()
under the hood and provide your component with the packet properties.
const UserList = (users = [], isLoading, hasAllLoaded, errors, loadUsers) => (
<div>
{errors && <ul>{errors.map(...)}</ul>}
{isLoading && <Spinner />}
<ul>{users.map(...)}</ul>
{hasAllLoaded || <button onClick={loadUsers}>Load users</button>}
</div>
);
import { consume } from 'react-packet';
import users from '../state/users';
import UserList from './user-list';
const ProjectUserList = consume(users.forProject(props => props.projectId))(UserList);
const GroupUserList = consume(users.forGroup(props => props.groupId))(UserList);
// <ProjectUserList projectId="projectA" />
// <GroupUserList groupId="groupA" />
You can call consume()
with multiple packets, but if any properties overlap, you'll have to combine them yourself with a mapPacketsToProps
:
const CompareUserLists = ({ listA, listB }) => (
<div>
<UserList {...listA} />
<UserList {...listB} />
</div>
);
const CompareUsersInGroups = consume(
[
users.forGroup(props => props.groupA),
users.forGroup(props => props.groupB)
],
(listA, listB) => ({
listA,
listB
})
)(CompareUserLists);
// <CompareUsersInGroups groupA="groupA" groupB="groupB" />