mofeiZ

Hi @vishwamartur, thanks for your contribution. This has already been fixed (see [playground example](https://0xeac7-forget.vercel.app/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwUYCASggGYC+BlMEGBA5DAgIZx7MA6AdpSh8uaCHwIBhRjj4I+eABQBKIvwIsSCAhgQYIzANxqCcMWEJtKBALwFNFSgr5QANi6VHxBNFYWWAdHCwbPI2ts5uKsDG6gFBMCGEtsDUnurUxgD0mZKMOqF4ABZalBBuEADuaHwA5gQu1VrVBHgQBKRalgC0nIhgYAQICbhgWTkuEDV+VIHBcngexmx4sOIAPAAmaABuAHzF5QQVuC4ba5lbe57UINRAA)). In general, we prefer to land fixes to the [core validation logic](https://github.com/facebook/react/blob/main/compiler/packages/babel-plugin-react-compiler/src/Validation/ValidateNoRefAccesInRender.ts) instead of ignoring specific...

Thanks for your contribution, but we're currently not accepting PRs to fix / change comments and internal errors. Closing as this is not a user facing error message or documentation.

> Overall looks good but see fixtures - looks like this causes us to take refs as deps in some cases which isn't quite right Ohh good catch. Debugged further...