# redux-saga-data

> A lib for fetching normalized data in a redux store through sagas.

Latest version **3.3.0** (published 2019-12-19) · MPL-2.0 license · 0 weekly downloads

## Install

```sh
npm install redux-saga-data
pnpm add redux-saga-data
yarn add redux-saga-data
bun add redux-saga-data
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 3.3.0 |
| Published | 2019-12-19 |
| First published | 2019-02-07 |
| Weekly downloads | 0 |
| License | MPL-2.0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 2 |
| Unpacked size | 53.5 KB |
| Known vulnerabilities | 0 |
| Install scripts | yes |
| GitHub stars | 7 |
| Maintainers | alwin, atusi, dbaudry, ledoux, nerocro, sixertoy |
| Keywords | redux, request, data, normalizer, redux-saga, saga |

## Links

- npm: https://www.npmjs.com/package/redux-saga-data
- Repository: https://github.com/betagouv/redux-saga-data
- Homepage: https://github.com/betagouv/redux-saga-data#readme
- Issues: https://github.com/betagouv/redux-saga-data/issues
- npm.io page: https://npm.io/package/redux-saga-data

## Dependencies (2)

- [redux-saga](https://npm.io/package/redux-saga.md) ^1.1.1
- [fetch-normalize-data](https://npm.io/package/fetch-normalize-data.md) 1.8.6

## Alternatives

- [@libsql/sqlite3](https://npm.io/package/@libsql/sqlite3.md) — 39.8K weekly downloads
- [@fortemi/core](https://npm.io/package/@fortemi/core.md) — 461 weekly downloads
- [cdb-converter](https://npm.io/package/cdb-converter.md) — 341 weekly downloads
- [@uplo/adapter-prisma](https://npm.io/package/@uplo/adapter-prisma.md) — 75 weekly downloads
- [typeorm-aios](https://npm.io/package/typeorm-aios.md) — 30 weekly downloads

## Recent versions

- 3.3.0 (latest) — 2019-12-19
- 3.2.1 — 2019-09-29
- 3.2.0 — 2019-09-27
- 3.1.10 — 2019-09-26
- 3.1.9 — 2019-09-26
- 3.1.8 — 2019-09-26
- 3.1.7 — 2019-09-24
- 3.1.6 — 2019-09-24
- 3.1.4 — 2019-09-24
- 3.1.3 — 2019-09-23
- 3.1.2 — 2019-09-23
- 3.1.1 — 2019-09-19
- 3.1.0 — 2019-09-19
- 3.0.1 — 2019-09-19
- 3.0.0-rc2 — 2019-09-19
- … 56 more at https://npm.io/package/redux-saga-data/versions

## README

<img alt="redux-saga-data logo" src="https://raw.githubusercontent.com/betagouv/redux-saga-data/master/icon.png" height=60/>

A lib for fetching normalized data in a redux store through sagas.

[![CircleCI](https://circleci.com/gh/betagouv/redux-saga-data/tree/master.svg?style=svg)](https://circleci.com/gh/betagouv/redux-saga-data/tree/master)
[![npm version](https://img.shields.io/npm/v/redux-saga-data.svg?style=flat-square)](https://npmjs.org/package/redux-saga-data)

## Basic Usage

You need to install a redux-saga setup with the watchDataActions and the data reducer:

```javascript
import {
  applyMiddleware,
  combineReducers,
  createStore
} from 'redux'
import createSagaMiddleware from 'redux-saga'
import { all } from 'redux-saga/effects'
import { createDataReducer, watchDataActions } from 'redux-saga-data'

const sagaMiddleware = createSagaMiddleware()
const storeEnhancer = applyMiddleware(sagaMiddleware)

function* rootSaga() {
  yield all([
    watchDataActions({
      rootUrl: 'http://momarx.fr',
    }),
  ])
}

const rootReducer = combineReducers({
  data: createDataReducer({ users: [] }),
})

const store = createStore(rootReducer, storeEnhancer)

sagaMiddleware.run(rootSaga)
```

Then you can request data from your api that will be stored
in the state.data

```javascript
import React, { Fragment } from 'react'
import { requestData } from 'redux-redux-saga'

class Foos extends Component {
  constructor () {
    super()
    this.state = { error: null }
  }

  componentDidMount () {
    const { dispatch } = this.props
    dispatch(requestData({
      apiPath: '/foos',
      handleFail: () => this.setState({ error: action.error }),
      method:'GET'
    }))
  }

  render () {
    const { foos } = this.props
    const { error } = this.state

    if (error) {
      return error
    }

    return (
      <Fragment>
        {foos.map(foo => (
          <div key={foo.id}> {foo.text} </div>
        ))}
      </Fragment>
    )
  }
}

function mapStateToProps (state) {
  return {
    foos: state.data.foos
  }
}

export default connect(mapStateToProps)(Foo)
```

NOTE: We could also used a handleSuccess in the requestData api, in order to grab the action.data foos in that simple case:

```javascript
constructor () {
  this.state = { error: null, foos: [] }
}

componentDidMount () {
  const { dispatch } = this.props
  dispatch(requestData({
    apiPath: '/foos',
    handleFail: () => this.setState({ error: action.error }),
    handleSuccess: () => this.setState({ foos: action.data }),
    method:'GET'
  }))
}

render () {
  const { error, foos } = this.setState
  ...
}
```

But if your rendered foos array should be coming from a memoizing merging (and potentially normalized) (and potentially selected from inter data filter conditions) state of foos, then syntax goes easier if you pick from the connected redux store lake of data.

## Usage with config

See all the possible config for requestData in the [fetch-normalize-data]( https://github.com/betagouv/fetch-normalize-data/tree/master) doc.

---
_Source: https://npm.io/package/redux-saga-data · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._