Point the seat, payment-method and add-on calls at routes that exist

Fixkamo-internal
Ya
5 Septemba 2026, 02:48 UTC
Mwandishi
Kamo
Ahadi ya
b7cc818

Four calls in posApi addressed REST-shaped URLs — /seats, /payment-method, /addons, DELETE /addons/{id} — and POSController exposes none of them. It has change-seats, change-payment-method, add-addon and remove-addon. So changing a subscription's seat count, its payment method, or its add-ons from the console had never worked: every one of them 404'd. Nothing surfaced it, because each is a fire-and-forget button whose failure looks like a toast, and remove-addon takes the instance id in a POST body rather than a path segment. This mattered enough to find now because two of those buttons had just been extended — the payment-method control gained WIRE and COMP, and the seat dialog was about to start charging money. The seat dialog now shows what the change will cost while the operator is still typing, debounced, asked of the server rather than computed here: a per-seat startup fee can be overridden by a negotiated agreement, and the figure in the dialog has to be the figure on the invoice. A preview that cannot be fetched leaves the dialog working and claims no fee, rather than blocking the change or asserting a zero.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei