You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider a scenario where a response has a nextLink that is an absolute URL. This URL typically has query parameters that control which page to return next such as $top and $skip. Those values are important and should be preserved when a request is sent to that URL but what happens instead is that those query values get overwritten with default values if exist in the mapper. See
Consider a scenario where a response has a
nextLink
that is an absolute URL. This URL typically has query parameters that control which page to return next such as$top
and$skip
. Those values are important and should be preserved when a request is sent to that URL but what happens instead is that those query values get overwritten with default values if exist in the mapper. Seeazure-sdk-for-js/sdk/core/core-client/src/urlHelpers.ts
Lines 142 to 146 in 1e507db
Notice that it calculates the query parameter value regardless of whether that query already exists in the absolute URL or not.
Then, default query parameter values get combined with existing ones by putting them in a set:
azure-sdk-for-js/sdk/core/core-client/src/urlHelpers.ts
Lines 253 to 274 in 1e507db
Which effectively replace the old ones with new ones.
The text was updated successfully, but these errors were encountered: