[fix]: handle mapping `timeout` -> `timeoutMs`
Merged
SE
8mo ago+13+13+01234567890123456789-2-2-0123456789
why
- the
timeoutMsparam ingotowas not being respected when using the stagehand api - the
/navigateroute on the server expectstimeout, while the actualgoto()implementation in node expectstimeoutMs
what changed
- added logic to correctly send the
timeoutMsparam to the server astimeout - added server side logic to map the
timeoutback totimoeutMs(which is whatgoto()expects)
screenshot: (navigate correctly adheres to defined timeout)
Summary by cubic
Fixes timeout handling for navigation by mapping timeoutMs on the client to timeout over the API, then back to timeoutMs for page.goto(). Navigations now respect the configured timeout when using the Stagehand API.
- Bug Fixes
- Client sends
timeoutto/navigatefromoptions.timeoutMs. - Server maps
timeouttotimeoutMsbefore callingpage.goto().
- Client sends