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.

Sign up for GitHub

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

Jump to bottom

Avoid mentioning source types of object literals in error messages #35250

Open
DanielRosenwasser opened this issue Nov 20, 2019 · 0 comments
Open

Avoid mentioning source types of object literals in error messages #35250

DanielRosenwasser opened this issue Nov 20, 2019 · 0 comments
Labels
Domain: Error Messages The issue relates to error messaging Experience Enhancement Noncontroversial enhancements
Projects
UX Sync

Comments

@DanielRosenwasser
Copy link
Member

Whenever a type that originates from an object literal is encountered, we should avoid writing out the whole type. It's rarely useful, and can get painful in a lot of contexts (think React Native styles objects).

- Type '{ goobledeyGock: string, tickTock: number, wakkaFlocka: { stuff: string } }' is not assignable to 'OneType | AnotherType'.
+ This object is not assignable to 'OneType | AnotherType'.
@DanielRosenwasser DanielRosenwasser added Domain: Error Messages The issue relates to error messaging Experience Enhancement Noncontroversial enhancements labels Nov 20, 2019
@DanielRosenwasser DanielRosenwasser added this to Agenda in UX Sync Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Domain: Error Messages The issue relates to error messaging Experience Enhancement Noncontroversial enhancements
Projects
UX Sync
  
Agenda
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DanielRosenwasser