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

react-use-handler

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react-use-handler

turn recreatable function to a persistent one

  • 1.2.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
39
increased by143.75%
Maintainers
1
Weekly downloads
 
Created
Source

useHandler

NPM version Build Status Coverage Status

TL;DR

In most cases useCallback hook should work for you. But if it doesn't, you're in the right place :)

What is it about?

This is an analogue of bound methods in class components, but for hooks. Here is an example of a class component:

  class ClassComponent extends React.Component {
    myHandler = (data) => {
      doSmth(data, this.props.prop1)
    }
    render() {
      return <ChildComponent onEvent={this.myHandler} />
    }
  }

or in a more brutal way

  class ClassComponent extends React.Component {
    constructor() {
      this.myHandler = this.myHandler.bind(this)
    }
    myHandler(data) {
      doSmth(data, this.props.prop1)
    }
    render() {
      return <ChildComponent onEvent={this.myHandler} />
    }
  }

myHandler method has access to actual props and state while ChildComponent receives the same instance of myHandler in its prop on every render. This feature can be usefull in some cases.

Use case #1.

Suppose you are using ChildComponent and want to get notifications from it on some events:

  <ChildComponent onCoolEvent={(data) => { /* .... */ })} />

Actually ChildComponent receives newly created instance of a function in onCoolEvent prop on each render. Sometimes it is not a problem, sometimes it is. Sometimes useCallback will help you. In case it's a problem and useCallback is not enough just wrap that function with useHandler like this

  <ChildComponent onCoolEvent={useHandler((data) => { /* .... */ })} />

useHandler guarantees that its return value will never change, but it'll always call the actual instance of your function with correct bindings.

Use case #2.

Suppose you are developing a component with some expensive async effects. Like so:

  const EffectiveComponent = ({ prop1, prop2, onFirstStage, onSecondStage }) => {
    /*...*/
    useEffect(() => {
      let mounted = true

      void async function () {
        // very expensive calculations1....
        if (!mounted) return
        onFirstStage()
        // even more expensive calculations2....
        if (!mounted) return
        onSecondStage()
      }()

      return () => { mounted = false }
    }, [prop1, prop2])
  }

Let's imagine you appreciate your effect very much and do not want to restart it if some of event props change. You want your effect to just do its work and emit some events. But there is a problem. If on... prop change you should restart your effect otherwise eventually it will call obsolete things. If you restart your effect on minor prop changes you can end up with some bad user experience.

To escape this you could make a ref, store there your event handler and then call it inside your effect without any trouble. But that's exactly what useHandler does! Let's use it:

  const EffectiveComponent = ({ prop1, prop2, onFirstStage, onSecondStage }) => {
    /*...*/
    const onFirstEvent = useHandler(onFirstStage)
    const onSecondEvent = useHandler(onSecondStage)

    useEffect(() => {
      let mounted = true

      void async function () {
        // very expensive calculations #1....
        if (!mounted) return
        onFirstEvent()
        // even more expensive calculations #2....
        if (!mounted) return
        onSecondEvent()
      }()

      return () => { mounted = false }
    }, [prop1, prop2])

    return /*....*/
  }

useHandler also handles the case when callback is actually undefined or null. In those cases it calls nothing and returns undefined.

API

Table of Contents

useHandler

This hook makes a proxy for a function. It guarantees to return the same instance across multiple renders. It calls nothing if the actual handler is nullish.

Parameters
  • f Func? Some being recreated function to wrap.

Returns Func function.

License

MIT © Vadzim Zieńka

Keywords

FAQs

Package last updated on 18 Jan 2020

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