Remove error list constraint #157
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
This would be very helpful, as it removes the requirement to maintain that list. Thanks, I'll wait for @yoavbls to take a look. |
Owner
|
I like it 🙂 |
yoavbls
approved these changes
Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @yoavbls, I’ve added over 400 error codes to TypeScript TV and modernized the error page UI.
Each error page now renders a single error, which improves rendering performance. As part of this change, I updated the URLs from
/errors/#ts${errorCode}to/errors/ts${errorCode}. But don't worry! Hash-based URLs are still supported for backward-compatibility. 🙂I also introduced a submission page so users can propose new error codes. When an unknown error code is encountered, the page still shows helpful information along with a submission form via comments (you can try it here: https://typescript.tv/errors/ts23001111/).
For the above reasons, I think we can remove the
KNOWN_ERROR_NUMBERSlimitation. Maintaining it required updates on both sides (your plugin and my site), and since the site now always renders meaningful content, it feels like the right time to simplify this.