Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
This depends largely on what "do something" you want to do, in response to a state change. If you just need to re-compute some other state: Write that as additional code in the component funct...
Answer
#6: Post edited
by
bignose
·
2025-01-28T00:18:36Z (25 days ago)
- This depends largely on what "do something" you want to do, in response to a state change.
- * If you just need to re-compute some other state: Write that as additional code in the component function.
- * If you need to have an effect on some *external system*: [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
* `setup`: The function to call, to set up the external effect. Returns a clean-up function, to call when unmounting this component.- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- ----
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
- In particular, you don't need to use an Effect simply to "do something" internal to the component. You just write that "do something" into the main code of the function; it is called every time to render the component.
- Rather, the purpose of `useEffect` is when your "do something" is specifically to have an effect *external to* the component itself.
- This depends largely on what "do something" you want to do, in response to a state change.
- * If you just need to re-compute some other state: Write that as additional code in the component function.
- * If you need to have an effect on some *external system*: [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
- * `setup`: The function to call, to set up the external effect. If clean-up is needed when the effect should stop, this function returns that clean-up function.
- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- ----
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
- In particular, you don't need to use an Effect simply to "do something" internal to the component. You just write that "do something" into the main code of the function; it is called every time to render the component.
- Rather, the purpose of `useEffect` is when your "do something" is specifically to have an effect *external to* the component itself.
#5: Post edited
by
bignose
·
2025-01-28T00:06:54Z (25 days ago)
[The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
* `setup`: The function to call, as an effect responding to a change in state.- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
- In particular, you don't need to use an Effect simply to "do something" internal to the component. You just write that "do something" into the main code of the function; it is called every time to render the component.
- Rather, the purpose of `useEffect` is when your "do something" is specifically to have an effect *external to* the component itself.
- This depends largely on what "do something" you want to do, in response to a state change.
- * If you just need to re-compute some other state: Write that as additional code in the component function.
- * If you need to have an effect on some *external system*: [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
- * `setup`: The function to call, to set up the external effect. Returns a clean-up function, to call when unmounting this component.
- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- ----
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
- In particular, you don't need to use an Effect simply to "do something" internal to the component. You just write that "do something" into the main code of the function; it is called every time to render the component.
- Rather, the purpose of `useEffect` is when your "do something" is specifically to have an effect *external to* the component itself.
#4: Post edited
by
bignose
·
2025-01-27T23:57:56Z (25 days ago)
- [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
- * `setup`: The function to call, as an effect responding to a change in state.
- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
In particular, you don't need to use an Effect simply to "do something" when rendering the component. You just write that "do something" into the main code of the function; it is called every time to render the component.
- [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
- * `setup`: The function to call, as an effect responding to a change in state.
- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
- In particular, you don't need to use an Effect simply to "do something" internal to the component. You just write that "do something" into the main code of the function; it is called every time to render the component.
- Rather, the purpose of `useEffect` is when your "do something" is specifically to have an effect *external to* the component itself.
#3: Post edited
by
bignose
·
2025-01-27T23:56:48Z (25 days ago)
- [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
- * `setup`: The function to call, as an effect responding to a change in state.
- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
- [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
- * `setup`: The function to call, as an effect responding to a change in state.
- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
- In particular, you don't need to use an Effect simply to "do something" when rendering the component. You just write that "do something" into the main code of the function; it is called every time to render the component.
#2: Post edited
by
bignose
·
2025-01-27T23:55:07Z (25 days ago)
- [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- To create the hook, you provide two arguments:
* The function to call, as an effect responding to a change in state.* The specific collection of state variables that should trigger this effect.
- [The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose.
- > useEffect is a React Hook that lets you synchronize a component with an external system.
- To create the hook, you provide two arguments:
- * `setup`: The function to call, as an effect responding to a change in state.
- * `dependencies` (optional): The specific collection of state variables that should trigger this effect.
- Note that the React documentation also warns: [You might not need an Effect](https://react.dev/learn/you-might-not-need-an-effect).
#1: Initial revision
by
bignose
·
2025-01-27T23:52:47Z (25 days ago)
[The `useEffect` hook](https://react.dev/reference/react/useEffect) is designed for this purpose. To create the hook, you provide two arguments: * The function to call, as an effect responding to a change in state. * The specific collection of state variables that should trigger this effect.