Allow to combine object shorthand notation with type assertion

[danielrentz]

Suggestion

🔍 Search Terms

object shorthand notation type assertion

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Allow to combine object shorthand notation with type conversions.

📃 Motivating Example

Using external libraries that are not typed very well.

function myFunc(type: string, data: unknown) {
  if (someExternalFunction(data)) {
    // here it's known that `data` is a string
    someOtherFunction({ type, data: data as string });
  }
}

It would be nice to be able to shorten this to

    someOtherFunction({ type, data as string });

or

    someOtherFunction({ type, <string>data });

💻 Use Cases

Just to make source code more concise.

[MartinJohns]

Last time this suggestion was closed due to lack of feedback and a comment to stay "well-clear of this syntactic space": #13035 (comment)

I think we want to stay well-clear of this syntactic space to keep room for future TC39.

[danielrentz]

Ok... The issue search function did not bring that thing up. (as usual when I try to use the search :) )

[typescript-bot]

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.