-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache the value-label pairs when the picker items are fetched #975
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Shaykoo thanks for the submission. Looking over the change, I think we need some functionality to reset that cache, to ensure we're not operating on outdated data if the underlying XML has changed.
if ( | ||
pickerItems | ||
.map((item: Element) => item.getAttribute('value')) | ||
.includes(value) | ||
) { | ||
const valueExists = pickerItems.some( | ||
item => item.getAttribute('value') === value, | ||
); | ||
if (valueExists) { | ||
return value; | ||
} | ||
if (pickerItems.length > 0) { | ||
return pickerItems[0].getAttribute('value') || ''; | ||
} | ||
return ''; | ||
return pickerItems.length > 0 | ||
? pickerItems[0].getAttribute('value') || '' | ||
: ''; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current getLabelForValue method loops through all picker items each time it is called. This can be inefficient if you have a large list of items. Caching the mapping of values to labels will improve performance.