packages/core/src/PinInput/PinInputInput.vue (1)

147-147: ⚠️ Potential issue | 🟠 Major

Type mismatch: Strings stored instead of numbers in numeric mode.

handleMultipleCharacter stores string values directly into tempModelValue, but when type="number", the model value type is number[] per the PinInputValue<'number'> definition. Compare with updateModelValueAt (line 175) which correctly converts to numbers with tempModelValue[index] = num.

This will cause the complete event to emit ['1', '2', '3', '4', '5'] (strings) instead of [1, 2, 3, 4, 5] (numbers) when pasting numeric characters.

🐛 Proposed fix to convert values in numeric mode

     if (context.isNumericMode.value && !/^\d*$/.test(value))
       continue

-    tempModelValue[i] = value
+    tempModelValue[i] = context.isNumericMode.value ? +value : value
     input.focus()

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/core/src/PinInput/PinInputInput.vue` at line 147,
handleMultipleCharacter currently assigns string characters into tempModelValue
(tempModelValue[i] = value), causing type mismatch when props.type === 'number';
change the assignment to convert the value to a number in numeric mode (e.g.,
tempModelValue[i] = props.type === 'number' ? Number(value) : value) following
the same conversion pattern used in updateModelValueAt so the emitted
model/complete events provide number[] for PinInputValue<'number'>.

packages/core/src/PinInput/PinInputInput.vue (1)

140-155: ⚠️ Potential issue | 🟠 Major

Decouple value cursor from input cursor to fully prevent numeric shifting

Line 144–150 still advances the input slot when a non-numeric character is skipped, so multi-character non-paste paths can still misalign digits in numeric mode.

Proposed fix

 function handleMultipleCharacter(values: string) {
   const tempModelValue = [...context.currentModelValue.value] as typeof context.currentModelValue.value
-  const initialIndex = values.length >= inputElements.value.length ? 0 : props.index
-  const lastIndex = Math.min(initialIndex + values.length, inputElements.value.length)
-  for (let i = initialIndex; i < lastIndex; i++) {
-    const input = inputElements.value[i]
-    const value = values[i - initialIndex]
-    if (context.isNumericMode.value) {
-      const num = Number.parseInt(value)
-      if (Number.isNaN(num))
-        continue
-      tempModelValue[i] = num
-    }
-    else {
-      tempModelValue[i] = value
-    }
-    input.focus()
-  }
+  const normalizedValues = context.isNumericMode.value
+    ? values.replace(NON_NUMBER_REG, '')
+    : values
+  const initialIndex = normalizedValues.length >= inputElements.value.length ? 0 : props.index
+
+  let inputIndex = initialIndex
+  let valueIndex = 0
+  while (inputIndex < inputElements.value.length && valueIndex < normalizedValues.length) {
+    const value = normalizedValues[valueIndex]
+    const input = inputElements.value[inputIndex]
+    tempModelValue[inputIndex] = context.isNumericMode.value
+      ? Number(value)
+      : value
+    input?.focus()
+    inputIndex++
+    valueIndex++
+  }
   context.modelValue.value = tempModelValue
-  inputElements.value[lastIndex]?.focus()
+  inputElements.value[inputIndex]?.focus()
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@packages/core/src/PinInput/PinInputInput.vue` around lines 140 - 155,
handleMultipleCharacter currently advances the input slot even when a
non-numeric character is skipped, causing misalignment in numeric mode; change
the loop to decouple the value cursor from the input cursor by using two indices
(e.g., slotIndex for inputElements and valueIndex for values) and iterate with a
while (slotIndex < lastIndex && valueIndex < values.length) so that when
context.isNumericMode.value and Number.parseInt(value) is NaN you only advance
valueIndex (skip that character) and do NOT increment slotIndex, and only
increment slotIndex when you successfully write into tempModelValue; keep using
tempModelValue, inputElements, initialIndex/lastIndex and then write back to
context.currentModelValue as before.