-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add final method call to request context header #478
Conversation
11e6c29
to
a1a7a69
Compare
@@ -141,11 +146,23 @@ export function createObjectSet<Q extends ObjectOrInterfaceDefinition>( | |||
asyncIter: async function*(): AsyncIterableIterator<Osdk<Q, "$all">> { | |||
let $nextPageToken: string | undefined = undefined; | |||
do { | |||
const result = await base.fetchPage({ $nextPageToken }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was there a reason that we call base.fetchPage
here instead of calling the unbound fetchPageInternal
? Or is the latter also fine?
aba07bd
to
353d3ec
Compare
@@ -148,7 +151,15 @@ export function createObjectSet<Q extends ObjectOrInterfaceDefinition>( | |||
ObjectOrInterfacePropertyKeysFrom2<Q>, | |||
boolean, | |||
"throw" | |||
> = await base.fetchPage({ $nextPageToken }); | |||
> = await fetchPageInternal( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To answer your previous question, I think we used base here so we wouldn't need to duplicate the fetchPageInternal code again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved after discussion, just lets make sure to comment the augmentRequestContext method
No description provided.