Change fetch.json() type to unknown

Open
#2,298 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Start by locating the generator source or generated declaration for fetch.json() and compare its current type with the NodeJS fetch type referenced in the issue. Trace how that declaration is produced, then verify that generated output uses unknown and run the repository's relevant generation or validation checks.

Written by the indexing model from the issue text.

Description

lib.d.ts bug
Summary

Follow NodeJS type and change to unknown

Expected vs. Actual Behavior

Please align with NodeJS fetch types

unknown is preferred over any and would be more precise because without validating received data one does not really know what has been received

Playground Link

No response

Browser Support
  • This API is supported in at least two major browser engines (not two Chromium-based browsers).
Have Tried The Latest Releases
  • This issue applies to the latest release of TypeScript.
  • This issue applies to the latest release of @types/web.
Additional Context

No response

Dominant language
TypeScript
Stars
740
Forks
474
Avg merge
2d 8h
Merged PRs (30d)
15

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/TypeScript-DOM-lib-generator

All issues in microsoft/TypeScript-DOM-lib-generator

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.