We have thousands of engineers committing React code every day to Meta’s largest codebases. Part of our responsibility on the Flow team is to make it as easy as possible for anyone to contribute, from design system React experts to C++ engineers making one-off internal pages to support their backend services. Over the last year, we’ve built several new language features to make it easier than ever
Likely to cause new Flow errors: We now require all generic functions to be fully annotated to prevent generic-escape issues. Some escaped-generic errors will be removed with missing-local-annot errors on return type annotation positions. Under LTI, we will no longer silently give unannotated parameters in destructuring assignment any type. Instead, they will be properly contextually typed. e.g. t
Local Type Inference: We are releasing a new inference mode called local type inference. You can enable this new mode in your codebase by adding inference_mode=lti to the [options] section in the flowconfig. We will describe more details on this inference mode in an upcoming blog post. Likely to cause new Flow errors: Unannotated class properties initialized with null will now errors. We now requi
On Sunday March 6, we migrated Stripe’s largest JavaScript codebase (powering the Stripe Dashboard) from Flow to TypeScript. In a single pull request, we converted more than 3.7 million lines of code. The next day, hundreds of engineers came in to start writing TypeScript for their projects. Seriously unreal. I remember a short time ago laughing at the idea of typescript ever landing at Stripe, an
How We Migrated from Javascript and Flow to TypeScript at Osome This fairy tale started a long time ago. Often, you make a bet on the wrong horse in life, but, unfortunately, you cannot do anything about it. You're always working with limited information (especially about the future), when making decisions, so essentially you are betting. This is life: sometimes it happens in your personal life an
Over the weekend, my team at @stripe converted the company's largest JS codebase from Flow to @typescript. We modif… https://t.co/041VgOss39
Likely to cause new Flow errors: Enforce that interfaces are supertypes of objects and classes. Also prevent objects from being a supertype of a class. Improve soundness of this typing by banning the unbinding of class methods (see https://medium.com/flow-type/sound-typing-for-this-in-flow-d62db2af969e). New Features: You can require an exhaustive check of an enum in a switch statement that includ
This domain is registered at NameSilo. If you are the owner, start administering it at NameSilo.com. If this is not your domain, find similar names that work for you. This webpage was generated by the domain owner using Sedo Domain Parking. Disclaimer: Sedo maintains no relationship with third party advertisers. Reference to any specific service or trade mark is not controlled by Sedo nor does it
Likely to cause new Flow errors: In Types First mode, exported classes and functions cannot be reassigned. Added similar checking of symbol in non-strict equality as other primitive types (example). We allow for non-strict equality checks between two symbol types, and between a symbol and null/void (example). We now write properties to unsealed objects recorded during speculative checking, after s
Adapted from “Phantom type” Haskell Wiki A phantom type is a parametrised type whose parameters do not all appear on the right-hand side of its definition, e.g class Data<M> { value: string; constructor(value: string) { this.value = value } }Here Data is a phantom type, because the M parameter doesn’t appear in its implementation. Why? An example: validating user inputSay you have a use(input: str
Hello! (And sorry for the radio silence.)A lot of our open-source users are rightfully observing that the Flow team has effectively stopped paying attention to an ever-growing list of issues and PRs on GitHub. And while there has been a lot of activity in terms of GitHub commits during this time, there has been little to no communication about our roadmap. We understand that this state of affairs
We recently ported MemSQL Studio's 30 thousand lines of JavaScript from using Flow to TypeScript. In this article, I describe why we ported our codebase, how it took place and how it has been working out for us. Disclaimer: my goal with this blog post is not to condemn Flow or usage of Flow. I highly admire the project, and I think that there is enough space in the JavaScript community for both ty
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く