Skip to content

The current 1.8 spec should feature a more prominent warning about being outdated #31369

Closed
@slikts

Description

@slikts

This relates to issues like #15711 and #21477, and the suggestion is to add a more prominent notice that the current spec is long out of date or legacy. A more visible notice is needed because the document's presence in the master branch under doc/spec.md suggests (at a glance) that the document would be current, and the version number and date at the top is easy to overlook and is bound to cause confusion (speaking from experience).

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA bug in TypeScript

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions