[New feature] add config to remove (or mark optional) some interfaces for a target browser version

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
tooling, web-dev

Research direction

No file, test, or entry point is identified. Start by examining the generator's existing configuration and browser-target support, then define how optional or removed interfaces should be selected and verify generated DOM typings for a target such as Chrome 75.

Written by the indexing model from the issue text.

Description

I did a POC in a local fork, it can configure a browser target, say Chrome 75, then it will mark APIs optional if they don't exist in chrome 75
If you think this is useful, I can create a PR for such feature

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.