SEZ9 commented on issue #10753: URL: https://github.com/apache/seatunnel/issues/10753#issuecomment-6228294056
@Rishavbhattarai — yes, the Typeform Source row is yours. Your check of `dev` matches what I see on this thread: nothing Typeform-related has been claimed or linked here, so there is no duplicate-claim concern. The v1 scope you outlined works for me, and following the Asana pattern is exactly right: that row is now complete, with the implementation, EN/ZH docs, registration, and offline E2E all landing through a single PR after the design note was settled on its own feature issue. Thanks to @saloni-eng for setting that template; please mirror it. I see you've since opened #12822 for the design note, so that part is done. What's left before code starts: - Confirm the open API details (the `before` cursor paging, `since` / `until` pass-through, and the 429/5xx backoff bounds) on #12822 so the incremental contract is pinned down first. - Keep the token strictly in the `Authorization: Bearer` header and out of params, logs, and job state, as you proposed — call that boundary out explicitly in the design note. - Keep all technical discussion on #12822; post back here only when the implementation PR is open and again when it merges, so I can move the row through "design review" → "in progress" → "done". Nothing else needed from you on this tracker right now. <!-- streview-comment:1804 --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
