SelectMenu label not displayed for falsy values

[ErwanLoop]

Environment

• Operating System: Windows_NT
• Node Version: v22.8.0
• Nuxt Version: 3.13.2
• CLI Version: 3.13.2
• Nitro Version: 2.9.7
• Package Manager: [email protected]
• Builder: -
• User Config: modules, plugins, css, colorMode, tiptap, runtimeConfig, nitro, routeRules, compatibilityDate
• Runtime Modules: @nuxt/[email protected], @pinia/[email protected], @vueuse/[email protected], [email protected]
• Build Modules: -

Version

v2.20.0

Reproduction

<script setup lang="ts">
enum DiscountType {
    Fixed = 0,
    Percentage = 1
}

const types = [
    {
        label: "€",
        value: DiscountType.Fixed
    },
    {
        label: "%",
        value: DiscountType.Percentage
    }
]
const type = ref<DiscountType>(DiscountType.Fixed)
</script>

<template>
    <USelectMenu v-model="type" :options="types" value-attribute="value" />
</template>

SelectMenu does not display the label associated to the falsy value "0":

The list is populated with both values:

The label associated to the truthy value "1" is displayed as expected:

Description

All falsy values are not displayed anymore since v2.20.0 due to the rework of the computed label in the SelectMenu component.

Here is the definition of this computed in /src/runtime/components/form/SelectMenu.vue:

const label = computed(() => {
      if (!props.modelValue) return null

      if (Array.isArray(props.modelValue) && props.modelValue.length) {
        return `${props.modelValue.length} selected`
      } else if (['string', 'number'].includes(typeof props.modelValue)) {
        return props.valueAttribute ? accessor(selected.value, props.optionAttribute) : props.modelValue
      }

      return accessor(props.modelValue as Record<string, any>, props.optionAttribute)
})

The component should treat 0, "" and false as "acceptable" labelled values.

I believe the first condition should be either :
if(props.modelValue == null) return null
Or:
if(props.modelValue === null || props.modelValue === undefined) return null

Additional context

I will try to find some time to create a pull request if this is accepted as an issue. Not sure I can manage to do it short-term though.

Logs