Closed shaydoc closed 2 years ago
This is specifically blowing up within the refreshLabels
function within useOptions
I'd love to help @shaydoc but please post a reproducible example. Also have you thought about using async options instead of computed and just returning locally stored results when it's below 50 hits?
@adamberecz I have worked around this issue, will close here, thanks for replying, great work!
Version
Description
When an option is selected and attempting to seacrch/filter the list, the error below arises. The issue is that the options list is computed and is set to react as the filter changes. the reasons are 2 fold. We have datasource, but if the datasource has less than 50 items we filter client side, else we filter via an api call. the data loading is also declarative in this instance.
Demo
See Fiddle here: JSFiddle error