@dialstack/sdk-dev / js/src / isPhoneNumberListReady
Function: isPhoneNumberListReady()
function isPhoneNumberListReady(
values,
issues,
maxNumbers): boolean;
Defined in: sdk/js/src/utils/phone-list.ts:433
The clean gate: an order may not advance while any row is unresolved.
Proceeding with a subset would quietly drop numbers the customer asked to port, and they would not find out until the port completed without them. A row is resolved by correcting it or deleting it — both deliberate acts.
A blank row is not a blocker: it is an unused field, and there is nothing on screen claiming it will be ported.
A repeat is a blocker, which it was not at first. The argument for letting it through was that nothing is lost at the carrier by sending a number once — true, and beside the point. The row stays on screen, so a list of 85 rows submits 83 numbers, and the two that vanish are exactly the kind of silent shortfall the rest of this design refuses. Deleting the repeat costs one click and makes what is on screen match what is ordered.
Parameters
values
readonly string[]
issues
readonly NumberIssue[]
maxNumbers
number
Returns
boolean