Skip to content

fix(commerce-elastic-path): requote from the managed form when the update returns no rates - #599

Merged
field123 merged 1 commit into
masterfrom
claude/managed-form-requote-fallback
Sep 28, 2026
Merged

field123 merged 1 commit into
masterfrom
claude/managed-form-requote-fallback

Conversation

@field123

Copy link
Copy Markdown
Collaborator

The loader bundle gives every app host the same package version, but each host's server routes stay on the version it installed. After #597, the managed form stopped requesting rates, because the update now returns them. A host still on an older server gets an address with no rates, so the shopper can't pick one and /pay fails.

The form now calls the requote once when the update returns an empty rate list. A current server returns the rates with the update, so it still sends one request per address change.

This keeps the next loader bump safe for app hosts that haven't upgraded their own server code yet.

…date returns no rates

The loader bundle ships one package version to every app host, while each
host's server routes stay on the version it installed. A host on an older
server clears the rates on an address change and does not requote, so the
new form left its shopper with no rate to pick and /pay failed.

The form now requotes once when the update comes back with an empty rate
list. Against a current server the update already carries the rates, so it
still sends one request per address change.
@field123
field123 merged commit c645b0d into master Sep 28, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant