You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to create an issue regarding the removal of the "What's new" overview page in the TypeScript documentation. While the handbook section explains TypeScript features, it does not provide version information, and without the overview page ( #2622 PR deleted the overview page), it is challenging to know which version introduced a specific feature and trace the related pull request. One single overview page was helpful to search keywords.
Recommended Fix:
I propose adding a feature to search keywords across all "What's new" pages or providing an alternative method to search for specific features and their introduction versions.
Could you please consider implementing this feature or suggest an alternative solution? Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered:
yo-goto
changed the title
Docs: Searching across all "What's new" pages
Docs: Searching keywords across all "What's new" pages
Mar 1, 2023
Hello! As per #2804, we are automatically closing all open issues. Please see #2804 for a description of what issues and PRs can be accepted going forward.
Issue:
I would like to create an issue regarding the removal of the "What's new" overview page in the TypeScript documentation. While the handbook section explains TypeScript features, it does not provide version information, and without the overview page ( #2622 PR deleted the overview page), it is challenging to know which version introduced a specific feature and trace the related pull request. One single overview page was helpful to search keywords.
Recommended Fix:
I propose adding a feature to search keywords across all "What's new" pages or providing an alternative method to search for specific features and their introduction versions.
Could you please consider implementing this feature or suggest an alternative solution? Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: