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
The recent PR #2708 introduced support for passing Headers instances, Map instances, and iterable objects as the headers argument to undici.request.
However, there have been no updates to documentation or types to reflect these changes.
This oversight needs to be addressed.
I'm considering fixing this issue, but I'd appreciate input from more experienced contributors like @mcollina, @metcoder95, @KhafraDev, and @mertcanaltin. Do any of you have suggestions or thoughts on how to approach this?
One approach I'm considering is extending the existing UndiciHeaders type with a definition similar to the following:
However, this may seem a bit verbose. I'm open to alternative suggestions or approaches.
It would also be helpful if someone could provide a checklist or guidelines for updating documentation and types in situations like this.
This could ensure that similar oversights are avoided in the future.
The text was updated successfully, but these errors were encountered:
The recent PR #2708 introduced support for passing
Headers
instances,Map
instances, and iterable objects as theheaders
argument toundici.request
.However, there have been no updates to documentation or types to reflect these changes.
This oversight needs to be addressed.
I'm considering fixing this issue, but I'd appreciate input from more experienced contributors like @mcollina, @metcoder95, @KhafraDev, and @mertcanaltin. Do any of you have suggestions or thoughts on how to approach this?
One approach I'm considering is extending the existing UndiciHeaders type with a definition similar to the following:
However, this may seem a bit verbose. I'm open to alternative suggestions or approaches.
It would also be helpful if someone could provide a checklist or guidelines for updating documentation and types in situations like this.
This could ensure that similar oversights are avoided in the future.
The text was updated successfully, but these errors were encountered: