mirror of
https://github.com/terribleplan/next.js.git
synced 2024-01-19 02:48:18 +00:00
3bbfbfad5c
* move imports into files using lettable operators, remove rxjs-library * refactor to be more in keeping with redux conventions from the single reducer.js, I split the functionality into actionTypes (actionTypes.js), actions (actions.js), and epics (epics.js). Most of the fetching should be done in an epic, but that requires introducing a new action and so was better in a separate commit. * switch to fetching on the front-end via an epic The fetching previously was triggered using an api call that had side effects, but was triggered from inside of an epic and was not an action. Now calls on the front-end all of the api calls are occuring via an action through fetchCharacterEpic. This does not remove the api.js file as I have not yet been able to get the epic to trigger correctly on the server-side, thus the api.fetchCharacter call is awaited in getInitialProps for initialising the state serverSide. * remove need for the serverSide api by directly handling the dispatch This still seems to be an incomplete solution to the problem as it circumvents the standard redux event flow on the serverside. However, it does obey the spirit of the redux event flow (as it passes an Observable of an action into the epic to then trigger other actions). Additionally, this removes the problem of code duplication. * update README.md and move lib/ to redux/ * Fix linting
6 lines
315 B
JavaScript
6 lines
315 B
JavaScript
export const FETCH_CHARACTER = 'FETCH_CHARACTER'
|
|
export const FETCH_CHARACTER_SUCCESS = 'FETCH_CHARACTER_SUCCESS'
|
|
export const FETCH_CHARACTER_FAILURE = 'FETCH_CHARACTER_FAILURE'
|
|
export const START_FETCHING_CHARACTERS = 'START_FETCHING_CHARACTERS'
|
|
export const STOP_FETCHING_CHARACTERS = 'STOP_FETCHING_CHARACTERS'
|