4 Commits

Include renames

Author	SHA1	Message	Date
Samuel SuslaandFacebook GitHub Bot	51af7cdcde	Use nested namespace name ... Summary: changelog: [internal] Enable two new clang tidy checks: - modernize-concat-nested-namespaces - google-build-using-namespace jest_e2e[run_all_tests] Reviewed By: rshest Differential Revision: D40020646 fbshipit-source-id: f3be80b5f829dd0ba376bdd70ed13332e114d48a	2022-10-13 05:07:59 -07:00
Samuel SuslaandFacebook GitHub Bot	ce50c43986	Add more clang tidy rules ... Summary: changelog: [internal] Add more clang tidy rules to prevent common class of bugs. Reviewed By: javache Differential Revision: D39245194 fbshipit-source-id: 5521c5c4653d7005b96ebba494e810ba5075afbc	2022-09-06 07:01:17 -07:00
Andres SuarezandFacebook GitHub Bot	8bd3edec88	Update copyright headers from Facebook to Meta ... Reviewed By: aaronabramov Differential Revision: D33367752 fbshipit-source-id: 4ce94d184485e5ee0a62cf67ad2d3ba16e285c8f	2021-12-30 15:11:21 -08:00
Samuel SuslaandFacebook GitHub Bot	34d189ae09	Introducing Leak Checker ... Summary: Changelog: [internal] Introducing LeakChecker. A tool that checks if all native components have been cleaned up when surface is stopped. **Known shortcomings**: - LeakChecker is only enabled in debug builds and the existence of leaks is logged to console. - For now, Leak Checker looks at N-1 screen. This is intentional as there is a known limitation of React that doesn't free up all shadow nodes when surface is stopped. Because of this, the use of LeakChecker is not intuitive and I'll work with React team to try to work around this. - It doesn't help locating the leak, it only informs that leak is present. I'll be looking into ways to help locate the leak. Reviewed By: JoshuaGross, mdvacca Differential Revision: D26727461 fbshipit-source-id: 8350190b99f24642f8e15a3c2e1d79cfaa810d3d	2021-03-17 02:57:37 -07:00