Reviewing files that changed from the base of the PR and between f1905e8 and 6c54a77.

• packages/bootstrap-vue-next/src/composables/useFormInput.ts (4 hunks)
• packages/bootstrap-vue-next/src/utils/debounce.ts (1 hunks)

• GitHub Check: build

packages/bootstrap-vue-next/src/utils/debounce.ts (4)

1-10: LGTM! Proper type imports and organization.

The imports are well-organized and properly typed using VueUse core types. This approach allows reusing established type definitions while implementing custom logic.

---

11-11: LGTM! Simple and effective no-op implementation.

The noop function is correctly implemented and will be useful for cleanup scenarios.

---

16-30: LGTM! Proper promise wrapper with cancellation support.

The createFilterWrapper function correctly wraps the filter to provide a promise-based interface while preserving the cancel method. The implementation properly handles the this context and argument passing.

---

103-109: LGTM! Well-documented export with proper typing.

The useDebounceFn function is properly typed and documented. The default values and return type correctly extend the base VueUse types with cancellation support.

packages/bootstrap-vue-next/src/composables/useFormInput.ts (6)

14-14: LGTM! Import cleanup maintains compatibility.

Good practice to keep the VueUse imports that are still needed while removing only useDebounceFn.

---

17-17: LGTM! Proper integration of local debounce utility.

The import correctly references the newly implemented local debounce utility.

---

31-31: LGTM! Improved number handling with nanToZero option.

Adding {nanToZero: true} ensures consistent behavior when dealing with invalid debounce values, preventing NaN from causing issues in timer logic.

---

50-57: LGTM! Well-implemented immediate update control.

The updateModelValue function enhancement properly supports both immediate and debounced updates. The logic clearly separates the two paths and maintains backward compatibility.

---

124-128: Excellent fix for the debounce blur issue!

This is the core fix that addresses the PR objective. The implementation correctly:

1. Cancels any pending debounced updates before comparing and updating the model value
2. Forces an immediate update on blur using the new immediate parameter
3. Maintains the existing force update logic

This ensures that blur events immediately update the model value, preventing the inconsistency described in the PR where transformations (like uppercase conversion) would be partially applied and then reverted.

---

111-117:

✅ Verification successful

Verify the early return condition logic.

The early return condition has been expanded to include debounceNumber.value <= 0. This seems logical since no debouncing would be needed when the debounce value is zero or negative.

---

🏁 Script executed:

#!/bin/bash
# Description: Verify the interaction between lazy modifiers and debounce values
# to ensure the early return logic is correct

# Search for any existing tests or documentation about the combination of these conditions
rg -A 10 -B 5 "lazy.*debounce|debounce.*lazy" --type ts --type vue

# Look for any existing blur event test cases
rg -A 15 -B 5 "onBlur|blur.*event" --type ts --type vue

Length of output: 182

---

🏁 Script executed:

#!/bin/bash
# Correct RG invocation to include .ts and .vue files via globs

# Search for any existing tests or documentation about lazy + debounce interactions
rg -g '*.ts' -g '*.vue' -A 10 -B 5 "lazy.*debounce|debounce.*lazy"

# Search for any existing blur event test cases
rg -g '*.ts' -g '*.vue' -A 15 -B 5 "onBlur|blur.*event"

Length of output: 21658

---

OnBlur early-return logic is correct

The added debounceNumber.value <= 0 check aligns with the common-props documentation—debounce only applies when set to a positive value and is ignored otherwise. Combined with the existing lazy, lazyFormatter, and trim flags, this condition ensures that on-blur formatting or flush behavior only runs when needed. No changes required.