Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Feature: [readonly-parameter-types et. al.] enhance allow option to allow @types/ built-ins #8572

Open
@arkapratimc

Description

@arkapratimc

Before You File a Proposal Please Confirm You Have Done The Following...

Relevant Package

type-utils

My proposal is suitable for this project

  • I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Description

A few lines of context -

  1. An old rfc - RFC: Common format to specify a type or value as a rule option #6017 (comment)
  2. StyleShit's comment on a PR on which I'm working - feat(eslint-plugin): [no-floating-promises] add an 'allowForKnownSafePromises' option #8502 (comment)

Steps to reproduce -

  1. go to https://stackblitz.com/edit/stackblitz-starters-tnrbtd?file=src%2Findex.ts
  2. run npx eslint src/index.ts in terminal
  3. check index.ts, line 4

Is typescript-eslint open to include a config option like {from: "package", name: "Foo", package: "data:text/javascript, export class Foo {};"}, or with the other URL schemes(like file:), in the eslint config file ?

There are 3 URL schemes in total - node:, file: & data:.
I think node: will be required to solve #8404. I just want to know about the other 2.

Additional Info

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issuebugSomething isn't workingpackage: eslint-pluginIssues related to @typescript-eslint/eslint-plugin

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions