MultiSelectField problems

[djb123]

Using latest (1.0.4) and the MultiSelectField components are not showing the options (even though I can confirm the data is there and in the correct value/label format), and when clicked it just shows the message "There are no matching items."

I am trying to push to prod soon, any timeframe on getting this fixed?

Thanks

[techniq]

Hey @djb123 👋. I just had a few minutes to look at this, but I see the problem.

let filteredOptions: MenuOption<TValue>[] = [...(options ?? [])];
let filteredSelectedOptions: MenuOption<TValue>[] = [...(selectedOptions ?? [])];
let filteredUnselectedOptions: MenuOption<TValue>[] = [...(unselectedOptions ?? [])];

filteredSelectedOptions and filteredUnselectedOptions are empty because selectedOptions and unselectedOptions are defined in reactive blocks and thus they are not in scope for non-reactive variables.

It should be fixing by changing this to...

$: filteredOptions: MenuOption<TValue>[] = [...(options ?? [])];
$: filteredSelectedOptions = [...(selectedOptions ?? [])];
$: filteredUnselectedOptions = [...(unselectedOptions ?? [])];

and my quick testing confirmed this

Before	After

I need to do more validation than I have time for right now before I feel comfortable releasing (running out the door). As a workaround, you can:

• Install the PR release package (and do some validation) using npm i https://pkg.pr.new/svelte-ux@595
• See if you spot any regressions with the docs
• Pass <MultiSelectField maintainOrder={true}> which should work around the issue (but have different handle of selected options

If all looks good to you, I'll push a release later tonight / tomorrow.

(cc: @brandonmcconnell looks like a regression we overlooked from this change)

[djb123]

Thanks man, you are the best! I bought more time, so I have until next week now. Thanks again

[techniq]

Welcome. Fixed in 1.0.6

[brandonmcconnell]

Good fix. Thanks for catching that and the quick turnaround, @techniq!