![]() In fact, we became involved to the point where we were championing the proposal! With its advancement to stage 3, we’re comfortable and proud to release it as part of TypeScript 3.7. Instead, our team recently took the steps to help drive the proposal to standardization, and ultimately to all JavaScript and TypeScript users. For years, we’ve been asked to implement the feature, but our stance has long been not to conflict with potential ECMAScript proposals. This one was filed over 5 years ago – before there was even a formal proposal within TC39. For context, there have been over 23,000 issues filed on the TypeScript issue tracker to date. Optional chaining is issue #16 on our issue tracker. TypeScript 3.7 implements one of the most highly-demanded ECMAScript features yet: optional chaining! Without further ado, let’s dive in and look at what’s new! Optional Chaining But if you’re the type of person who likes to learn by getting their hands dirty, check out the TypeScript playground where we’ve added an entire menu for learning what’s new. This is a pretty extensive list! If you’re into reading, you’re in for some fun with this release. Local and Imported Type Declarations Now Conflict.Build-Free Editing with Project References.The useDefineForClassFields Flag and The declare Property Modifier.Better Support for never-Returning Functions.We’ve got a lot of great features in TypeScript 3.7, including: Following directions for Visual Studio Code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |