packages/components/date-picker-panel/__tests__/date-picker-panel.test.tsx (1)

1189-1225: Convergence case is well-tested.

This is the important boundary test — it locks in the behavior that a fully-disabled span between minDate and minDate+1month collapses both endpoints to minDate rather than leaving maxDate on a disabled day. Consider adding a symmetric convergence test for the 'max' branch (entering an end date when every prior month day is disabled) to guard against future regressions in the type === 'max' path.

🤖 Prompt for AI Agents

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

In `@packages/components/date-picker-panel/__tests__/date-picker-panel.test.tsx`
around lines 1189 - 1225, Add a symmetric test that verifies the 'max'
convergence path: create a test like the existing one but set disabledDate (the
same function) to disable dates on/after 2026-03-21, mount DatePickerPanel with
v-model bound to the same value ref, locate the right-side input via pickerss
(the same query used earlier) using
'.el-date-range-picker__time-picker-wrap:nth-child(2) input' and simulate
changing the end date to '2026-03-20' (dispatch input and change events and
await nextTick()), then assert that value[0] and value[1] both format to
'2026-03-20' and that disabledDate(value[0])/disabledDate(value[1]) return
false; this mirrors the existing 'min' convergence test but exercises the type
=== "max" branch.

packages/components/date-picker-panel/src/date-picker-com/panel-date-range.vue (1)

783-795: Logic is correct — convergence to minDate is handled.

I traced the edge case where every day in (minDate, minDate+1month] is disabled: when cursor reaches minDate + 1 day, the isAfter(minDate.value) check passes, the loop body subtracts one day (cursor becomes minDate, which is guaranteed non-disabled by the early-return at Line 770), then assigns adjustedMax = minDate and breaks. So adjustedMax is never left at the original disabled minDate+1month value. Nice handling.

One optional suggestion: this block is nearly identical to the max branch at Lines 807–819 except for direction. Consider extracting a helper to reduce duplication:

♻️ Optional helper extraction

const findNonDisabledBoundary = (
  start: Dayjs,
  boundary: Dayjs,
  direction: 'backward' | 'forward'
): Dayjs => {
  if (!disabledDate || !disabledDate(start.toDate())) return start
  let cursor = start
  const step = direction === 'backward' ? -1 : 1
  const predicate =
    direction === 'backward'
      ? () => cursor.isAfter(boundary)
      : () => cursor.isBefore(boundary)
  while (predicate()) {
    cursor = cursor.add(step, 'day')
    if (!disabledDate(cursor.toDate())) return cursor
  }
  return cursor
}

🤖 Prompt for AI Agents

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

In
`@packages/components/date-picker-panel/src/date-picker-com/panel-date-range.vue`
around lines 783 - 795, The duplicated logic that searches for the nearest
non-disabled date around minDate/maxDate should be extracted into a reusable
helper (e.g., findNonDisabledBoundary) to remove the near-identical blocks
around adjustedMax/minDate.value and the later max-branch; implement a function
that accepts start Dayjs, boundary Dayjs, and direction ('backward'|'forward'),
encapsulates the disabledDate checks and the while-loop cursor movement, and
then replace the current loops that set
adjustedMax/rightDate.value/maxDate.value and the corresponding max-side code to
call this helper and assign its result.