mboperator/react-dataloader

It loads the data!

react-dataloader

We built the data loading layer so you don't have to.

Why

The main purpose of this component library is to take care of data loading, store generation, and persistence so that you can focus on views instead of data fetching.

What's included:

• ObjectLoader
• Datasource
• DependentDatasource
• FilteredDatasource
• Examples

Usage

// Somewhere
var exampleConfig = {
  name: "Parents",
  idAttribute: "id",
  basePath: "http://localhost:8083/api/",
  endpoint: "checklists",
  storeType: "shared"
};

// In your render function
<Datasource {...exampleConfig}>
  <SomeViewComponent>
</Datasource>

• SomeViewComponent should expect to receive (array) collection, (object) actions, and any other props passed to Datasource

At Procore we use it in this way

<Datasource {...exampleConfig}>
  <Collection>
    <ChecklistCell onSelect={this.onSelect}/>
  </Collection>
</Datasource>

• Collection can be thought of as a layout component, its inputs are an (array) collection, (object) actions, and a (ReactComponent) cell. It maps over collection and returns cells.
• This approach allows us to quickly create customizable lists by simply swapping out the layout cell, and the endpoint we're hitting.

react-dataloader's Issues

Custom store method support

Store extensions must

• Create corresponding actions
• Allow for analagous synchronizer actions

Todo

• Draft options for store extension
• ???

Explore switching to Immutable

Areas of concern

• Query performance
• Significance of rerendering performance gains

Clean up url builder support

Should be 1-1 with synchronizer actions instead of recycling.

Expose default store class

To allow for easy subclassing for custom stores.