fix(PinInput): remove default generic type

[KIM-DONGJU]

🔗 Linked issue

❓ Type of change

• 🐞 Bug fix (a non-breaking change that fixes an issue)

📚 Description

This PR updates the PinInput component to support 'number' as a valid value for the type prop.

Previously, the component only accepted 'text', which limited use cases where numeric input was desired (e.g., PIN codes, OTPs). While the documentation suggested that both 'text' and 'number' were supported, the actual type definition restricted the type prop to string only—resulting in a TypeScript error when attempting to use type="number".

This fix corrects the type definition to explicitly allow both 'text' and 'number', aligning the implementation with the documented behavior and ensuring type safety without affecting existing functionality.

Changes include:

• Updated defineProps to explicitly support both 'text' and 'number' types

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@4346

commit: 02b1b45

[benjamincanac]

Indeed, this change is necessary there should be no default here. However, the playground should work with just string[] since the default type is text 🤔

[benjamincanac]

That's what I was looking into but not there are no string[] | number[] definition. The Reka UI component defines it like this: type PinInputValue<Type extends PinInputType = 'text'> = Type extends 'number' ? number[] : string[]. This should work, I'm confused 😅

[KIM-DONGJU]

I've looked into this as well, and it does correctly infer the type of the complete event when type="text" is explicitly specified, like in <UPinInput type="text" @ complete="onComplete" />.
However, I'm also unsure why TypeScript fails to infer the correct type when relying on the default type value.

[KIM-DONGJU]

@benjamincanac
Additionally, could you let me know the estimated release schedule for the version that includes reka-ui 2.3.1 (e.g., 3.1.4)?
Currently, it seems there's an issue where, in the current version, when the PinInput type is set to number, trying to clear the value results in it changing to 0 instead of being cleared.