fix(examples, tests): use useUpdateAtom and write-only atoms to avoid re-render

[liby]

Response to the call for this issue

The utility hooks can get big. I need someone to volunteer to help it, especially for documentation & examples.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/pmndrs/jotai/AxkR7Aa5QqLHeU91FBcuJ3LwdeUU
✅ Preview: https://jotai-git-fork-liby-master-pmndrs.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit d8c400e:

Sandbox	Source
React	Configuration
React Typescript	Configuration

[dai-shi]

Thanks for your help.
Having best practices in examples is nice.
Using utils in utils tests is ok.

However, I would like to keep tests/*.test.tsx to depend only on core (no utils).
It's intentional/acceptable to have extra re-renders there (not important for tests).
If it were issues, we would make write-only atoms (that's the suggestion for core-only solution).

If you can adjust it, please go ahead. I can take it over if you like.

[liby]

@dai-shi
I've revised it. Could you take another review of it for me?

It's intentional/acceptable to have extra re-renders there (not important for tests).
If it were issues, we would make write-only atoms (that's the suggestion for core-only solution).

If necessary, I can undo changes other than utils tests and examples.

[dai-shi]

Looks good. As I said, I don't think it's very important to avoid re-renders in some of core tests, but someone may learn coding pattern from tests, so it'd be good as you suggest.

[liby]

but someone may learn coding pattern from tests

Yes, that's why I kept the comments in the sample code.