合并原作者的更新 #3523
合并原作者的更新 #3523
Conversation
Updated CONTRIBUTING.md: Mention of "facebook.com" was not a link
rename `Id` suffix to `ID` to apply naming conventions
Warn if a non-object value is used in ReactFragment.create
Update to CLA, CONTRIBUTING.md
This ensures that we have a prefix that can be easily identified in logs so that we can filter out warnings based on their prefix. This also turns the remaining two monitorCodeUse callers into warnings. We'll probably still use monitorCodeUse until we know if we want to deprecate but most releases should only have warnings.
Moar warnings with solid prefixes!
More lint rules, fixes
safe_yaml 1.0.3 has some issues with Ruby 2.2.0: dtao/safe_yaml#67
Fix for the jekyll docs build process
ESLint coverage
Only monitor components that are likely stateful (inputs and composites)
Update jsx binary to latest jstransform + latest flow syntax features
Fixed Copyright year for three files and react.js licence to BSD-license
Update AUTHORS for 0.13
Missed updating this in facebook#3283 before merging.
Some minor burried docs.
ES6 Class Docs
ReactDOMComponent should not accept children for void elements
…ments_consistancy make dev and production environment consistent
Add displayName to nested render warnings [facebook#1726]
This is in response to facebook#3207 to address concerns regarding third-party scripts and browser plugins potentially altering DOM nodes within document.body, causing problems with reconciliation. Closes facebook#3211.
Add numeric CSS property - stroke width
Revert "Revert facebook#1536"
…ss-type-usage Fix comment to reflect the new (non-deprecated) way of accessing a class type.
…e-warn Check that console exists before warning
Bringing the code to one style.
initialize dev variables in dev mode only in shouldUpdateReactComponent.js
warn if IE8 is in compatibility mode
shallowEqual: bail if either argument is falsey
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks! |
|
Can you post title and description of this in English please? You'll also want to rebase because there is a ton of noise here. Also also, don't try to merge into gh-pages. You should target master. |
|
@zpao I think he was trying to merge from facebook to his own fork, but hit the wrong button. |
|
Maybe, that's somehow related to the DDoS attack which is taking place on GitHub right now.to the DDoS attack which is taking place on GitHub right now. |
|
Alright, reopen if this was intended and we can discuss further. |
20 participants
如题