TypeScript 4.3 supports type specification for properties

TypeScript 4.3 supports type specification for properties

Now available in beta, the upgrade to Microsoft’s typed JavaScript also introduces an override keyword and improvements to template string types.

Credit: Dreamstime

TypeScript 4.3, a planned upgrade to Microsoft’s typed superset of JavaScript, allows developers to specify types for reading and writing to properties.

This type specification enhancement addresses a situation in which modeling APIs that convert values in TypeScript has required picking between “being precise” and “being permissive.” By being precise, developers could make reading values easier but writing them harder. By being permissive, they could make writing values easier but reading harder.

TypeScript 4.3 is available in beta release as of April 1. A release candidate is due on  May 11, and the production release on May 25.

Other features planned in TypeScript 4.3 include the addition of an override keyword, whereby a method marked with this keyword will make sure that a method with the same name exists. When extending classes in JavaScript, the language makes it easy to override methods, but there are mistakes that can be made, such as missing renames. A noImplicitOverride flag makes it an error to override any method from a superclass unless the developer explicitly uses the override keyword.

Improvements to template string types are also in the works, including better relating and inferring between different template string types. TypeScript now does the work to prove whether or not each part of a template string can successfully match.

Meanwhile, more class elements can be given #private#names to make them truly private at runtime. In addition to properties, now methods and accessors can be given private names, as can static members. Under strictNullChecks, an error will be triggered when checking whether a Promise is “truthy” in a conditional.

Delving deeper, index signatures, which allow developers to set more properties on a value than a type explicitly declares, now can be declared as static. Previously, they could only be declared on the instance side of a class.

When an import statement does not have a path, a list of possible imports will be provided. When developers commit a full completion, the full import statement will be completed including the path that was going to be written. TypeScript now can understand @Link tags and will try to resolve declarations they link to.

TypeScript 4.3 can be accessed through NuGet or via NPM using the command npm install typescript@beta. TypeScript 4.2 was published as a production release on February 23, featuring enhancements pertaining to tuple types and type aliases.

Tags Microsoft


Show Comments