Skip to main content

Trigger event depending on local state on component unmount in React

I have a component with some internal state that is not being propagated throughout the application just on certain events.

const FunComponent = (initialDescription, onSave) => {
  const [description, setDescription] = useState('initialDescription');

  const handleDescriptionSave = () => {
    onSave(description);
  }

  return ( ... );
}

My issue is that the component can get unmounted by something higher up in the component tree, and at that point I would want to force-trigger onSave. Great - i thought - I can just write a useEffect with an empty dependency array, and it will be run on unmount.

The issue is that both the onSave prop and the description state is something my useEffect cleanup depends on.

If I add them to the dependency array, it will save with the previous description value on every description change. I don't want that. If I don't add them to the dependency array, it will just use the initial onSave and description value on unmount.

const FunComponent = (initialDescription, onSave) => {
  const [description, setDescription] = useState(initialDescription);

  const handleDescriptionSave = () => {
    onSave(description);
  }

  useEffect(() => {
    return () => { onSave(description) };
  }, [onSave, description])

  return ( ... );
}

What hack I came up with is to store the callback in a ref, and have an effect to keep it up to date, and call the ref on unmount:

const FunComponent = (initialDescription, onSave) => {
  const [description, setDescription] = useState(initialDescription);

  const handleDescriptionSave = useCallback(() => {
    onSave(description);
  }, [onSave, description]);

  const handleDescriptionSaveRef = useRef(handleDescriptionSave);

  useEffect(() => {
    handleDescriptionSaveRef.current = handleDescriptionSave;
  }, [onSave, description]);

  useEffect(() => {
    return () => { handleDescriptionSaveRef.current(); };
  }, []);

  return ( ... );
}

But this seems super-duper hacky.

Is there a general recommended pattern for this I fail to recognise? Will this fail in some way? Is this a good solution?

Via Active questions tagged javascript - Stack Overflow https://ift.tt/c7G8lvS

Comments

Popular posts from this blog

Prop `className` did not match in next js app

I have written a sample code ( Github Link here ). this is a simple next js app, but giving me error when I refresh the page. This seems to be the common problem and I tried the fix provided in the internet but does not seem to fix my issue. The error is Warning: Prop className did not match. Server: "MuiBox-root MuiBox-root-1" Client: "MuiBox-root MuiBox-root-2". Did changes for _document.js, modified _app.js as mentioned in official website and solutions in stackoverflow. but nothing seems to work. Could someone take a look and help me whats wrong with the code? Via Active questions tagged javascript - Stack Overflow https://ift.tt/2FdjaAW

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console