Issue with "Inject on first request" not setting offset to 0 in version 6.36.0

[deluxebear]

Description: When selecting the "Inject on first request" option, the offset is not set to 0 during the request. This issue persists in version 6.36.0, whereas version 6.17.0 works as expected.

Steps to Reproduce:

Select the "Inject on first request" option in the settings.
Make the request.
Observe that the offset is not set to 0 in version 6.36.0.
Expected Behavior: The offset should be set to 0 when the "Inject on first request" option is selected.

Environment:

Version 6.36.0
Version 6.13.0 works correctly

[natikgadzhi]

Christo Grabowski (@ChristoGrab) could be a regression after the nested request options work?

[ChristoGrab]

Hmm could be, I'll see if we can pinpoint the regression to that update 👀

[deluxebear]

[bazarnov]

Fixed in two steps: #482 (6.45.2) for syncs, where the first page token 0 was treated as falsy and never injected, and #691 (6.60.14) for Connector Builder test reads, which used a separate single-page path until then.

On current main the first request carries offset: 0 for every injection type (request parameter, header, body data, body JSON with field_name or field_path, alongside a requester-level request_body_json), in a regular read, a Builder test read and the manifest server. Closing as fixed. Please reopen if it still happens on a current version.