BUG/ [Routerlicious-Driver]Add undefined value handling in restWrapper #25737
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes an issue in the @fluidframework/routerlicious-driver package, specifically in restWrapper.ts, where the function axiosBuildRequestInitConfig was directly accessing requestConfig.headers without checking if it was undefined.
When headers is undefined, the code fails during request initialization, causing runtime errors.
Root Cause
The existing implementation assumed that requestConfig.headers would always be defined:
headers: requestConfig.headers as Record<string, string>,
However, in some cases, the Axios request configuration does not include headers, leading to failures when attempting to spread or cast an undefined value.
Breaking Changes
Reviewer Guidance
The review process is outlined on this wiki page.