James Ritchie
d6786002b2
* tasks no longer inside a group in the side menu (and added “cron”) * Delay using a timezone * Added React Not Defined error to the troubleshooting page * Improved the React common problem * Link to v2 docs * New Development section and entry in Common Problems * Concurrently running the terminal * Fixed the .env weirdness * Added section on creating PATs for Github actions * Improved the Machine spec and limits page * Quick start steps now have nice images * Added a diagram for the lifecycle functions * Added note about onFailure * CRON -> cron/Cron * WIP adding more steps to the next.js guide * WIP next.js * WIP adding tabbed steps for pages/app router * References to Infisical links to their homepage so it’s clearer * WIP updating the nextjs guide * WIP nextjs guide * More nextjs guide steps * More copy * Added rate limit trouble shooting * Removed old prisma error title * Added secret key step * Added a note for logging in using a specified domain if self hosting * typo * App router docs copy * Deploy copy update * Added a favicon.png to fix a docs build error * Removed unused snippet * Server actions now inside a tab * Server actions + restructured the triggering section * Added troubleshooting snippet for react event handlers * Added a new troubleshooting snippet for ESM * Updated old replaying image to reflect the new UI * Removed references to reattempting * Updated replaying from the run page * Added a bulk replay section * Updated the writing tasks intro page * Removed edge runtime code for now * Added edge runtime – it seems to just work! * import type
17 lines
600 B
Plaintext
17 lines
600 B
Plaintext
### Correctly passing event handlers to React components
|
|
|
|
An issue can sometimes arise when you try to pass a function directly to the `onClick` prop. This is because the function may require specific arguments or context that are not available when the event occurs. By wrapping the function call in an arrow function, you ensure that the handler is called with the correct context and any necessary arguments. For example:
|
|
|
|
This works:
|
|
|
|
```tsx
|
|
<Button onClick={() => myTask()}>Trigger my task</Button>
|
|
```
|
|
|
|
Whereas this does not work:
|
|
|
|
```tsx
|
|
<Button onClick={myTask}>Trigger my task</Button>
|
|
```
|
|
|