content can be undefined because of some timing issues. the Cell is rendered before the new data is loaded when navigating between content types in the CM list views.
There is a depper issue to fix for v5 but it it's still valid to check the value is defined and is an array before accessing that length prop regardless
Why is it needed?
Fix a bug
How to test it?
Navigating in the CM between content-types with repeatable components displayed in the list view should not reproduce the error anymore
What does it do?
content can be undefined because of some timing issues. the Cell is rendered before the new data is loaded when navigating between content types in the CM list views.
There is a depper issue to fix for v5 but it it's still valid to check the value is defined and is an array before accessing that length prop regardless
Why is it needed?
Fix a bug
How to test it?
Navigating in the CM between content-types with repeatable components displayed in the list view should not reproduce the error anymore
Related issue(s)/PR(s)
Fix https://github.com/strapi/strapi/issues/19660