React: accessor function don't trigger when data is outside of exported component

从链接的 CodeSandbox 开始，尤其是 /src/NoWorks.tsx，并在 English 和 Netherlands 之间切换时，将其组件外数据与正常工作的示例进行比较。确认 accessor 函数是否在重新渲染期间被跳过，然后追踪 v8.5.15 中涉及的 React 表格行为。当 accessor 执行且两个示例中渲染出的翻译都更新时，即表示完成。

Describe the bug

We faced an issue regarding some cells in our application not triggering their translations correctly.

Looking at the attached codesandbox you can see 2 examples. One working and one not.
We discovered that when data is defined outside the export of the component .accessor function don't trigger as expected.

Your minimal, reproducible example

https://codesandbox.io/s/i18next-react-table-forked-2znx8c?file=/src/NoWorks.tsx

Steps to reproduce

1. Go to https://codesandbox.io/s/i18next-react-table-forked-2znx8c?file=/src/NoWorks.tsx
2. Open console
3. On default you see 'en' language logged by both the 'works' and 'noWorks' component.
4. Click on Netherlands button
5. You will see the 'works' rendered language console.log inside 'columnHelper.accessor' does correctly trigger
6. You will also see the counter for 'noWorks' triggered but the rendered language console.log inside 'columnHelper.accessor' don't trigger
7. Click on English button and see step 5 to 6 repeated.

Expected behavior

As a User I am expecting the accessor function to trigger despite the DataTable data being imported from outside the component or initiated inside the component.

How often does this bug happen?

Every time

Screenshots or Videos

No response

Platform

• OS: macOS, Windows
• Browser: Chrome, Safari, Firefox

react-table version

v8.5.15

TypeScript version

v4.8.4

Additional context

No response

Terms & Code of Conduct

• I agree to follow this project's Code of Conduct
• I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.