select does not like options value containing raw numerical zero

The input selector acts wiggy when you define it to have an option element that is the number 0.

For instance.

timeZones: [-11, -10, -9, -8, -7, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14],
timeZone: 0,

{{#power-select options=timeZones selected=timeZone searchEnabled=false onchange=(action (mut timeZone)) as |opt|}}
                    {{opt}}
{{/power-select}}

What happens is that the selection is not displayed if the selected is set to 0 and also when you scroll to the selection in the UI it auto-scrolls back to the top of the window.

[cibernox]

yeah, I’m sure there is at least a couple places where I’m checking something like if (selectedOption) { do foo } where I should do if (selectedOption !== undefined) { do foo }.

In my opinion, 0, false and null are perfectly valid options. The only value that should represent the absence of an option, is undefined

[SirZach]

I can reproduce the same unselected behavior with false as the value