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
Hi, I'm trying to figure out if I should use @key attribute in my Blazor WASM app. In my scenario I use Virtualize component to display customer search results. All results are loaded at once. I'm using Virtualize so that only the results that are currently visible to the user are rendered. The list of items only changes when a new search query is submitted and the list now references the new results. Each row displays customer details like photo, first name, last name, etc. So far I'm not using @key attribute and haven't noticed any problems. I'm wondering if I should use it.
Will using @key give any benefits in this scenario?
Is using @key attribute with Virtualize component always a good idea?
How can I measure if @key attribute causes an improvement or not in my app?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm trying to figure out if I should use
@key
attribute in my Blazor WASM app. In my scenario I useVirtualize
component to display customer search results. All results are loaded at once. I'm usingVirtualize
so that only the results that are currently visible to the user are rendered. The list of items only changes when a new search query is submitted and the list now references the new results. Each row displays customer details like photo, first name, last name, etc. So far I'm not using@key
attribute and haven't noticed any problems. I'm wondering if I should use it.Will using
@key
give any benefits in this scenario?Is using
@key
attribute withVirtualize
component always a good idea?How can I measure if
@key
attribute causes an improvement or not in my app?Beta Was this translation helpful? Give feedback.
All reactions