I think your principle is good, but this is going too far to throw out react.
You really just want to split those things out of the UI component and keep minimal code in the component file. But having it be code free is too much for real client side apps.
Modern apps have very interactive UI that needs code. Things like animation management(stop/start/cancel) etc… have subtle interactions. Canvas zoom and pan, canvas render layouts that relate to UI, etc… lots of timing and control code that is app state dependent and transient and belongs in components.
I apply the simple principle and move any app state management and business logic out of the component UI code. But still lean into logical code in UI.
You really just want to split those things out of the UI component and keep minimal code in the component file. But having it be code free is too much for real client side apps.
Modern apps have very interactive UI that needs code. Things like animation management(stop/start/cancel) etc… have subtle interactions. Canvas zoom and pan, canvas render layouts that relate to UI, etc… lots of timing and control code that is app state dependent and transient and belongs in components.
I apply the simple principle and move any app state management and business logic out of the component UI code. But still lean into logical code in UI.