Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
slikts opened this issue May 13, 2019 · 1 comment
Labels
Bug A bug in TypeScript
Milestone

Comments

@slikts
Copy link

slikts commented May 13, 2019

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).

@RyanCavanaugh RyanCavanaugh added the Bug A bug in TypeScript label May 13, 2019
@RyanCavanaugh RyanCavanaugh added this to the Backlog milestone May 13, 2019
@jakebailey
Copy link
Member

This is an old issue, but in #51791 I deleted the spec wholesale; I don't think it gets more prominent than "doesn't exist".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A bug in TypeScript
Projects
None yet
Development

No branches or pull requests

3 participants