Description
rel-events is an awesome events library for react. It uses redux behind the scenes to offer a more convenient, simple, and relevant API for dealing with data flows.
rel-events alternatives and similar libraries
Based on the "Redux" category.
Alternatively, view rel-events alternatives based on common mentions on social networks and blogs.
-
Reactime 6.0: State Debugger for React
Developer tool for time travel debugging and performance monitoring in React applications. -
#<Sawyer::Resource:0x00007f8b44d36950>
基于React开发的新一代web调试工具,支持React组件调试,类似于Chrome Devtools。A Lightweight, Easy To Extend Web Debugging Tool Build With React -
react-redux-api-tools
A set of tools to facilitate react-redux development and decouple logic from compontents
CodeRabbit: AI Code Reviews for Developers
Do you think we are missing an alternative of rel-events or a related project?
README
rel-events
To read the docs, go to our docs folder. :) To see the app demo, go to our codesandbox page!
Welcome to the rel-events
github repo!
rel-events
is an awesome events library for react. It uses redux
behind the scenes to offer a more convenient, simple and relevant API for dealing with data flows.
Basic Usage
Installing
To install rel-events
, just run npm i --save rel-events
.
If you wish to use Events to make HTTP Requests (which you probably do), there's another step to set things up. Follow our HTTPEvents Guide to have everything ready. :)
With that done, you may start to create some events!
Creating a basic Event
Let's say you want to pass a range of dates from DatePickerComponent
to CalendarComponent
. Instead of creating actions and reducers, forget everything about redux; create an Event instead.
To do that, you need to initialize a new Event. It's recommended you create it in a new file (events.js
).
// on events.js
import { Event } from 'rel-events';
export const ChooseDateRangeEvent = new Event({
name: 'chooseDateRange',
manager: {
initialState: {},
onDispatch: (state, event) => {
return {
...state,
startDate: event.startDate,
endDate: event.endDate,
}
}
}
});
Let's break step-by-step what this code means:
First, you import the Event class from our lib, then instantiate a new event. This Event receives an object with two required keys: name
and manager
. While name
is self-explanatory, manager
is not.
For default Events, an Event Manager should have an initialState
and implement an onDispatch
method, which will be called whenever the event is dispatched. This is the alternative to the reducer part of the default redux flow.
We recommend using classes for your EventManagers as well, since we can decouple Events from their managers.
// on eventManagers.js
export class ChooseDateRangeEventManager {
initialState = {};
onDispatch = (state, event) => {
return {
...state,
startDate: event.startDate,
endDate: event.endDate,
}
}
}
}
Then:
// on events.js
import { Event } from 'rel-events';
import { ChooseDateRangeEventManager } from './eventManagers.js';
export const ChooseDateRangeEvent = new Event({
name: 'chooseDateRange',
manager: new ChooseDateRangeEventManager(),
);
Hooking it up with redux
With the event instantiated, you need to hook it up to redux so it can be dispatched and save data. When creating your root reducer, you should import the Event and initialize its reducers.
// on myAppRootReducers.js
import { combineReducers } from 'redux';
import { combineEventReducers } from 'rel-events';
import { ChooseDateRangeEvent } from './events.js';
// remember to use object spread, so it's set up correctly
export default combineReducers({
...combineEventReducers([ ChooseDateRangeEvent ]),
});
Notice the store names and reducers aren't declared anymore; you don't need to. Any Event object will deal with anything and everything redux related. To be able to do that, you only need to hook it to redux as the example above. To see more on how this works, read our how it works docs.
Now you have our Event ready to go! Now, you just need to register it to a Component, which can trigger it and/or listen to it.
Registering components to Events
Let's say you have a component called DatePickerComponent
that knows how to render a beautiful date picker. It has a handleDatesChange
method to update the state with the new dates.
export default class DatePickerComponent extends React.Component {
//...
handleDatesChange = (startDate, endDate) => {
this.setState({ startDate, endDate });
}
//...
}
To be able to send data from this component to the CalendarComponent
, you may register both Components to your Event. Whenever you register a Component to an Event, you automatically receive a function to trigger the event as a prop. The function's name is the same as the event name you passed when initializing the event.
import { ChooseDateRangeEvent } from './events.js';
// you won't export the component directly anymore
class DatePickerComponent extends React.Component {
//...
handleDatesChange = (startDate, endDate) => {
// here, the event passing the new dates is triggered
// after setState is done
this.setState(
{ startDate, endDate },
() => this.props.chooseDateRange({ startDate, endDate })
);
}
//...
}
// and here, you register the component to the event.
// since Components are mostly named with CamelCase,
// we preferred to name the key like that as well
export default ChooseDateRangeEvent.register({
Component: DatePickerComponent,
});
// you may as well register a Component to multiple events, no worries;
// just remember to only export after you're done registering the Component to your events
Then, you may register your CalendarComponent
as well, but passing a new props
key:
import { ChooseDateRangeEvent } from './events.js';
class CalendarComponent extends React.Component {
//...
render(){
const { startDate, endDate } = this.props;
return <h1>The dates are: {startDate}, {endDate}</h1>
}
}
// and here, you get the props from the event
export default ChooseDateRangeEvent.register({
Component: CalendarComponent,
props: ['startDate', 'endDate'],
})
And that's it! We still have a lot of other features to discuss, but I'll talk about those later. Before that, let's talk about using events to make HTTP requests.
Contributing
Thanks for wanting to contribute! Please, read our Contributing guide carefully before opening PRs, though. We do enjoy PRs, but any PRs that don't follow our contributing guidelines will probably be rejected :/
Thanks
Thanks for everyone at Labcodes for giving me the structure and time for me to work on this pet project of mine and giving me lots of awesome feedback! Bernardo Fontes, Luan Fonseca, Thulio Philipe, Mariana Bedran, Breno Chamie and Renato Oliveira, I'm really, really grateful for your input! <3