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
React Ensure we're using the latest object-assign, which has protection against a non-spec-compliant native Object.assign. (@zpao in #6681) Add a new warning to communicate that props objects passed to createElement must be plain objects. (@richardscarrott in #6134) Fix a batching bug resulting in some lifecycle methods incorrectly being called multiple times. (@spicyj in #6650) React DOM Fix regr
Whoa, a new version of Immutable! The big news is that we now export types for both Flow and TypeScript in the npm module! Also that pesky length warning has finally been fully removed. There are also a good amount of small bug fixes and performance improvements. Finally, the API docs have been improved greatly! Check it out http://facebook.github.io/immutable-js/docs/. A huge huge thanks to every
This repo contains attribute-driven-API cookbooks maintained by Facebook. It's a large chunk of what we refer to as our "core cookbooks." It's worth reading our Philosophy.md doc before reading this. It covers how we use Chef and is important context before reading this. It is important to note that these cookbooks are built using a very specific model that's very different from most other cookboo
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
This is a contrived example of using Immutable structures as React state. This example assumes React v0.13 or higher. v0.13 provides the functional setState API and allows for Iterables to be used as React children. This example also uses some ES6 features (destructuring, and arrow functions). Note that state must be a plain JS object, and not an Immutable collection, because React's setState API
* This source code is licensed under the BSD-style license found in the * LICENSE file in the root directory of this source tree. An additional grant
I don't really think it has any benefit to keep waitFor method in dispatcher as it's leading to wrong design. A great example of that is implementation in flux-chat. I was actually thinking about sending a PR where waitFor method is not used, then I realised that the only correct way would be to get rid of ThreadStore and UnreadThreadStore. I believe the right approach would be to to keep entire s
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く