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
You will notice when we create the rows for the metadata table, that the name property can be two different things. Either a string or a react component. The name property is also used as a key for our metadata table entries. This triggers the react error, because more than one entry has a key [object Object] (from the object name entries).
The text was updated successfully, but these errors were encountered:
kpsherva
transferred this issue from inveniosoftware/invenio-app-ils
Jun 2, 2020
Fixed by #193.
The name property should only be passed a string value; and it makes sense, otherwise it can break the layout. As it turns out, the only use case for having a node was to have an icon before the text, which is a very valid reason. This was addressed by adding an optional icon property (of type node).
You will notice when we create the rows for the metadata table, that the
name
property can be two different things. Either a string or a react component. Thename
property is also used as akey
for our metadata table entries. This triggers the react error, because more than one entry has a key[object Object]
(from the object name entries).The text was updated successfully, but these errors were encountered: