Skip to content

doc: record package naming considerations wrt excessive broadness #70

Description

@DerekNonGeneric

This package allows for excessive broadness in scope and am having trouble coming up w/ what should be stated in this repo's VISION file. It may likely be the case that the naming can be improved to be focused.

See: typescript-eslint/typescript-eslint#4172

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions