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

TypeScript 3.0 improved error UX meta-issue #25310

DanielRosenwasser opened this issue Jun 28, 2018 · 0 comments

TypeScript 3.0 improved error UX meta-issue #25310

DanielRosenwasser opened this issue Jun 28, 2018 · 0 comments


Copy link

@DanielRosenwasser DanielRosenwasser commented Jun 28, 2018

In TypeScript 3.0, we're aiming for a better error message experience all around.

One of the related efforts we've been working on is related error spans: #25257.

However, in addition to that, we've received enough constructive feedback about error messages that we can act on.

TypeScript 3.0

  • Better JSX attribute errors (#23117)
  • Better errors on object properties (#22170, #25030)
  • Smarter elaborations when assigning Foo<T> to Foo<U> | Bar<V> (#24776)
  • Smarter elaborations when assigning objects to Foo | Bar[] (#25750 )
  • Better guidance for non-existent deep imports (#24781)
  • Better errors on always true/false conditions (#25245)
  • Smarter elaborations against Foo | null | undefined (#25086)
  • Better truncation on big types (#24778)
  • Better duplicate declaration errors (#25324)

TypeScript 3.x

These suggested improvements didn't make it in time for 3.0, but we'll hopefully continue working on them! Check out #26077 to keep track of them.

  • Better hints for uncalled types (#25308)
  • Better hints for 'cannot find name' errors (#25309)
  • Better errors on weak type intersections like IntrinsicAttributes (#24146 🏃‍♂️)
  • Better errors when matching implementation signatures (#25488)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant