You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Custom components with fields of type list do not always re-render when props change.
To Reproduce
Steps to reproduce the behavior:
Create custom component with list type
Render list
Change props (title in this example)
Expected behavior
Expect both renders of the list to update as the props change.
Screenshots
Additional context
It seems that adding optional chaining when using the list props for some reason works, even though the props are initialised with a default value so technically the contents of the field list shouldn't ever be undefined. Or alternatively I would expect to see an error when accessing the title or items props. I have observed this only for list type fields.
Describe the bug
Custom components with fields of type
list
do not always re-render when props change.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect both renders of the list to update as the props change.
Screenshots
Additional context
It seems that adding optional chaining when using the list props for some reason works, even though the props are initialised with a default value so technically the contents of the field list shouldn't ever be undefined. Or alternatively I would expect to see an error when accessing the title or items props. I have observed this only for list type fields.
The text was updated successfully, but these errors were encountered: