Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

fetch-component-data

Package Overview
Dependencies
Maintainers
1
Versions
30
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

fetch-component-data

Small util functions for Frameworkstein

  • 7.0.14
  • Source
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

fetch-component-data

Data fetching helper and Redux middlware for React components in Frameworkstein apps

fetchComponentDataMiddleware

Redux middleware to ensure container components get a chance to load their data when they're mounted. Detects redux-router or react-router-redux route change actions and calls fetchComponentData on the component of the route that is being navigated to.

This middleware is much the same as adding a call to fetchData in each component's componentDidMount function.

fetchComponentData

Calls Component.fetchData on a list of React Components. Used to tie in the data loading story for Frameworkstein.

Best used in conjunction with redux-request-middleware or another method of returning a promise from dispatched actions. See there for more detailed docs.

Used internally by fl-react-server.

There's no magic here, just a convenience function that enforces the fetchData convention.

// MyPage.js

export default class MyPage extends React.Component {

  // Middleware will call this method on each route change
  // The store is provided, we can get the current state of the router from it via redux-router
  // We'll also need its dispatch method to dipatch actions from here
  // May return a promise or call the given callback function. Only useful if doing server side rendering, so the server renderer can delay rendering the page until the component has finished loading its data.
  static fetchData({store, action}/*, callback*/) {

    // As is the current action if we're transitioning between routes. 'action.payload' contains the props for the route we're transitioning to. Here for example we're getting router.params.id from it
    const { router } = store.getState()
    const id = ((action && action.payload && action.payload.params) || router.params).id
    
    // Assuming we're using redux-request-middleware to return a promise when dispatching this action
    return store.dispatch(loadMyPageContent())
  }

  // ...rest of the component goes below

  render() {
    // ...etc
  }
}

FAQs

Package last updated on 24 Oct 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc