You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
This release includes major changes to Flow's model for React. The following links contain detailed documentation on the new model. Defining components Event handling ref functions Typing children Higher-order components Utility type reference Please use the new flow-upgrade tool to upgrade your codebase to take advantage of these changes! Likely to cause new Flow errors: We are modifying how you
Notable bug fixes: Optimized performance when typechecking classes Optimized performance of sentinel property checks involving large enums Lots of libdef updates! Thanks everyone for the contributions! Misc: Fixed infinite recursion from array spread Added experimental support for sending errors to an IDE over a persistent connection Removed unused --libs flag on status, check, and start commands
New Features: Experimental support for "lazy" typechecking. On large codebases, the Flow server will start up faster when using the --lazy flag with flow start or flow server, by only computing dependency information and not doing any typechecking. Instead, as files are touched, they are typechecked incrementally along with files that depend on them (and their dependencies). Relatedly, running flo
Likely to cause new Flow errors: We are now sealing the object type that is passed to a React component's props. This means Flow will start complaining if you try and access unknown React props. Strict function call arity checking is now on for everyone! The experimental.strict_call_arity option has been removed. For more, see https://flow.org/blog/2017/05/07/Strict-Function-Call-Arity/ Notable bu
Likely to cause new Flow errors: We updated the type for the React.Component constructor, which means Flow can now infer the prop types based on the super(props) call in a react component constructor. This means components that weren't already declaring their prop types may start getting errors if there are any issues with their prop types. We fixed the type of Promise.prototype.catch, which means
Likely to cause new Flow errors: Previous usage of ReactElement<*> as a return type for render functions in React may now cause new errors now that a type propogation bug has been fixed. The general solution for this is to remove the return type for functions that return a React element (return types can be inferred by Flow, and Flow has never had a good way to express the type of a specific React
Likely to cause new Flow errors: Dictionary types (i.e. {[key: string]: ValueType}) were previously covariant which proved to be a significant source of unsoundness. Dictionary types are now invariant by default in order to fall into consistency with other collection types. It is possible to opt in to explicit covariance with new syntax: {+[key: string]: ValueType}, but note that this is now enfor
Likely to cause new Flow errors: Significant fix to matching members of union types. This fix very likely surfaces typechecking issues that were missed before. Check out the blog post for more details Variables in template literals are now subject to the same rules as variables being concatenated with a string using +. This may surface template strings with variables that may not safely coerce to
Likely to cause new Flow errors: When you refine a mixed variable with typeof myVar === 'object', we used to refine the type of myVar to null | Object. Now it is refined to null | {[key: string]: mixed}. This means myVar.prop has the type mixed rather than any. Removed non-standard Promise methods. Previous versions of Flow specified the type of Promise.prototype.done and Promise.cast, which are n
###v0.12.0 Likely to cause new Flow errors: Fixed a bug where declarations from libraries which are exported from one module are not checked properly in the module into which that module is imported (e.g. if A.foo() returns a Promise, and module B requires A and calls A.foo(), the return type of A.foo() was not being checked properly) Fixed enforcement of Object and Function type annotation arity,
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く