{"push_id":1149036487,"size":60,"distinct_size":60,"ref":"refs/heads/master","head":"9a93f1c3c4c793010ef5fa31b38f78e0100f1d13","before":"57e117f1feddc0746740f9cb1cb4a9ca9aa8329f","commits":[{"sha":"4acf009284bfbcd3408b0f198358112de1bcba28","author":{"name":"Andrei Coman","email":"d5e386d5c97d4d88a93d874b42d2c222be9fc591@fb.com"},"message":"Pass resource drawable id to constructor directly\n\nSummary:\nInstead of passing the helper to each method that uses it, just pass it\nto the image constructor.\n\nReviewed By: dmmiller\n\nDifferential Revision: D3364532\n\nfbshipit-source-id: 949bdbf951875c9b8cd05d028a2c329e12d72042","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/4acf009284bfbcd3408b0f198358112de1bcba28"},{"sha":"2aad61650e2e9c47de0ac692ea08148da5ad552d","author":{"name":"Konstantin Raev","email":"262a3feb6c5718f8f9d3bda3bc4169ca50eb70b8@fb.com"},"message":"Open sourced more instrumentation tests #1\n\nReviewed By: avaly\n\nDifferential Revision: D3366104\n\nfbshipit-source-id: 1c77b29e28726a6a105317d9f6944bbf78b707d7","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/2aad61650e2e9c47de0ac692ea08148da5ad552d"},{"sha":"a8d4fbb5b2ed57e077f96340c926e57f0633955c","author":{"name":"Mike Grabowski","email":"97babb7adaf42d77e40f5469542cc28be6e7f46d@gmail.com"},"message":"Add upcoming releases to the schedule\n\nSummary: Closes https://github.com/facebook/react-native/pull/7947\n\nDifferential Revision: D3392139\n\nfbshipit-source-id: aa7c0dd760d4922e44eb1b36e8d4f599d81ba680","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/a8d4fbb5b2ed57e077f96340c926e57f0633955c"},{"sha":"329c7168975a508de535ea7809ddd1d8c6ab5455","author":{"name":"Nick Lockwood","email":"c3998cc0d63bddc85da2da582ab467453b0e9127@fb.com"},"message":"Fixed bug where layoutSubviews was called continuously for scrollview\n\nSummary:\nRCTScrollView was calling `dockClosestSectionHeader` in `reactBridgeDidFinishTransaction`, which triggers a layout update. The reason for this was in case the `stickyHeaderIndexes` property was updated, which would require the headers to be adjusted.\n\nHowever, doing this in `reactBridgeDidFinishTransaction` had the affect of causing `layoutSubviews` to be called repeatedly every frame even if nothing had changed and the scrollview wasn't moving, which was especially expensive when combined with the `removeClippedSubviews` logic, that loops through every view to calculate if it needs to be clipped.\n\nThis fix moves the `dockClosestSectionHeader` call into `didUpdateProps`, and checks that the stickyHeaderIndexes have actually changed before calling it.\n\nReviewed By: javache\n\nDifferential Revision: D3387607\n\nfbshipit-source-id: c71e00c6fac48337a63d7fee7c7c23e016acf24e","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/329c7168975a508de535ea7809ddd1d8c6ab5455"},{"sha":"873149499088d25c130742fc7b3d90e7ef280e6f","author":{"name":"dragonwong","email":"e6031a3a5f00310bececf03b2f81e0659d8e88bd@qq.com"},"message":"change leftButton init position\n\nSummary:\nIn navigationBar, when back to the previous view, the left button of the previous view should fade in like iOS native navBar, instead of move in. It's interesting that the right button acts correct.\n\nReact Native:\n\n![clear](https://cloud.githubusercontent.com/assets/2622602/15535443/fa5e77bc-229f-11e6-8632-0dd9f5f2fb26.gif)\n\niOS Native:\n\n![clear2](https://cloud.githubusercontent.com/assets/2622602/15535452/05999918-22a0-11e6-877c-63590b7bb9ef.gif)\nCloses https://github.com/facebook/react-native/pull/7745\n\nDifferential Revision: D3392307\n\nPulled By: nicklockwood\n\nfbshipit-source-id: e5384140049bf7b6f78fc093209ee48814a2ffdc","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/873149499088d25c130742fc7b3d90e7ef280e6f"},{"sha":"1048e5d3445094393298d4e818ff04c41f4e56a7","author":{"name":"Nick Lockwood","email":"c3998cc0d63bddc85da2da582ab467453b0e9127@fb.com"},"message":"Fixed removeClippedSubviews\n\nSummary:\nThe `removeClippedSubviews` feature works by umounting views from the hierarchy if they move outside the bounds of their parent.\n\nThis was previously restricted to clipping views which had `overflow: hidden`, since we cannot efficiently check whether the subviews of a view go outside its bounds, and so clipping a view that has potentially overflowing children becomes an expensive recursive operation.\n\nThe problem with this is that `overflow: visible` is the default, and it's not well documented nor easy to tell that `removeClippedSubviews` has been set up correctly (i.e. with all children having `overflow: hidden`).\n\nWhen I checked, I found that `removeClippedSubviews` was not working on any of the examples in UIExplorer, nor in several of our internal apps, because the views inside the ListView has `overflow: visible`. This was probably caused by an infra change at some point, but I'm not sure how long it's been broken.\n\nIt's vanishingly unlikely that anyone would ever deliberately want subviews to overflow their bounds in this scenario, so I've updated the logic to simply ignore the `overflow` property and assume that views should be clipped if you are using the `removeClippedSubviews` property on the parent.\n\nCons / Breaking changes: in some rare circumstances, a view might get clipped prematurely if its parent is outside the scrollview bounds, but it itself is inside. This doesn't occur in practice in any of our products, and could be worked around with additional wrapper views if it did.\n\nPros: removeClippedSubviews is now much easier to use, and much more likely to work as intended, so most list-based apps should see a performance improvement.\n\nReviewed By: javache\n\nDifferential Revision: D3385316\n\nfbshipit-source-id: 1c0064a4c21340a971ba80d794062a356ae6cfb3","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/1048e5d3445094393298d4e818ff04c41f4e56a7"},{"sha":"72b363d7fc1bf0b9fe5226d5e1a31141ea144614","author":{"name":"Nick Lockwood","email":"c3998cc0d63bddc85da2da582ab467453b0e9127@fb.com"},"message":"Replaced isMainThread checks with a proper test for main queue\n\nSummary:\nAs per https://twitter.com/olebegemann/status/738656134731599872, our use of \"main thread\" to mean \"main queue\" seems to be unsafe.\n\nThis diff replaces the `NSThread.isMainQueue` checks with dispatch_get_specific(), which is the recommended approach.\n\nI've also replaced all use of \"MainThread\" terminology with \"MainQueue\", and taken the opportunity to deprecate the \"sync\" param of `RCTExecuteOnMainThread()`, which, while we do still use it in a few places, is incredibly unsafe and shouldn't be encouraged.\n\nReviewed By: javache\n\nDifferential Revision: D3384910\n\nfbshipit-source-id: ea7c216013372267b82eb25a38db5eb4cd46a089","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/72b363d7fc1bf0b9fe5226d5e1a31141ea144614"},{"sha":"4de616b4c1a9d3556632a93504828f0539fa4fa5","author":{"name":"Pieter De Baets","email":"377831b9cd0f79984db1fb62440ca394156e97b4@fb.com"},"message":"Remove deprecated calls from StatusBarIOS\n\nReviewed By: nicklockwood\n\nDifferential Revision: D3346701\n\nfbshipit-source-id: 17809a4cd686f3b431257e85d85770aee640bbc9","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/4de616b4c1a9d3556632a93504828f0539fa4fa5"},{"sha":"5b4b02747792c77b51c64449bc18b9a0ba81f867","author":{"name":"Joshua Pinter","email":"d459a6dba3808a05cfd03a67b7068b5cff69d79c@gmail.com"},"message":"Add get scheduled local notifications\n\nSummary:\n_(This is a remake of #6907, which I botched pretty good with a rebase.)_\n\nThis returns an `Array` of Local Notifications that have been scheduled to be delivered.\n\nAvailable attributes on return Notification object (if set in the local notification itself):\n\n`alertAction`\n`alertBody`\n`applicationIconBadgeNumber`\n`category`\n`fireDate`\n`soundName`\n`userInfo`\n\nMore could be added to this but I just matched what was available in the `Object` passed to `presentLocalNotification` and `scheduleLocalNotification`.\n\n**Motivation**\n\nI needed to determine the number and other details about local notifications that were already scheduled. There is an API for this in iOS but one hadn't been built yet for React Native.\n\nI created the Obj-C method and updated the documentation in `PushNotificationIOS.js` as well.\n\n**Usage:**\n\n```js\nPushNotificationIOS.getScheduledLocalNotifications( (notifications) => {\n  console.log(notifications);\n});\n```\n\n**Sample Output:**\n\n```js\n[\n  Object {\n    aler\nCloses https://github.com/facebook/react-native/pull/7937\n\nDifferential Revision: D3392476\n\nPulled By: javache\n\nfbshipit-source-id: d83f419bfcfbdaf9b955724dcf5cfe26834895fb","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/5b4b02747792c77b51c64449bc18b9a0ba81f867"},{"sha":"61046c3195da29296f540255bd602bdb2742181f","author":{"name":"Siqi Liu","email":"ae4a0336777d71ff9ea6588e2e7de37e09cb842e@fb.com"},"message":"Fix the bug where key shortcuts are invoked in TextInputs in iOS\n\nSummary:\nThis is a followup for \"Add Shortcut \"Double R\" to Reload JS in iOS\".\nPlease see the previous two revisions:[[ D3371536 | D3371536 ]], [[ D3343907 | D3343907 ]]\n\nIn previous revisions, we only tested with the iOS UIExplorer app, without testing in the iOS Catalyst app, where the key shortcuts we added are always invoked in TextInput components. It's due to a bug with the `UIApplicationDelegate`. Just fix this bug in this revision and successfully tested in the Catalyst app.\n\nReviewed By: mkonicek\n\nDifferential Revision: D3391045\n\nfbshipit-source-id: 8b76fbfe7592218b02dd22502d25eebbc59f3cbc","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/61046c3195da29296f540255bd602bdb2742181f"},{"sha":"f3507f99f18f8a26d67289fbad4d52e1f15a294c","author":{"name":"Dave Miller","email":"c74099f40d9478e558e5cd604b023d9e82612d14@fb.com"},"message":"Remove support for password property and only use secureTextEntry\n\nSummary:\nReduce the public surface area of TextInput.  It only exposes a secureTextEntry property, but on Android was also accepting password as a prop.\nThis removes that.\n\nReviewed By: javache\n\nDifferential Revision: D3392223\n\nfbshipit-source-id: 67c36fbe16fe493e2841d5d9deb78e3be2209ebd","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/f3507f99f18f8a26d67289fbad4d52e1f15a294c"},{"sha":"4e3a8343b353b51b716dcebbbdb14bc2f92a89c8","author":{"name":"Tom Walters","email":"d61bf940720e8e6ca9117937669db7e833a60755@cantarus.com"},"message":"Convert warning about keystore into warning block in SignedAPKAndroid.md\n\nSummary:\nThe current docs page [Generating a Signed APK](https://facebook.github.io/react-native/docs/signed-apk-android.html) contains a note about keeping your generated keystore safe, but this isn't well highlighted.\n\nThis commit highlights the notice in a warning blockquote to ensure people following the guide don't miss the importance of keeping the keystore safe as shown below:\n\n<img width=\"666\" alt=\"screen shot 2016-06-06 at 10 01 25\" src=\"https://cloud.githubusercontent.com/assets/1863808/15817245/10e4e6d2-2bcf-11e6-9fe8-defc8a6ec93c.png\">\nCloses https://github.com/facebook/react-native/pull/7948\n\nDifferential Revision: D3393005\n\nfbshipit-source-id: e9c2666a79134eccc1b1868fe850ee896e63266e","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/4e3a8343b353b51b716dcebbbdb14bc2f92a89c8"},{"sha":"44c9cf3a917cd7efd3e5569f47fb1aa8b53587b7","author":{"name":"Nick Lockwood","email":"c3998cc0d63bddc85da2da582ab467453b0e9127@fb.com"},"message":"Refactored subview management\n\nReviewed By: javache\n\nDifferential Revision: D3392214\n\nfbshipit-source-id: 6f16841df5cf866dda5ac27dd244e266ec85a86e","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/44c9cf3a917cd7efd3e5569f47fb1aa8b53587b7"},{"sha":"42a5568419fb1fea6ffdd59725f065949d799a7f","author":{"name":"Alexey Lang","email":"6a77cb51e2272c02e8cf24f9756292d0514d630a@fb.com"},"message":"Change API for using custom JSC\n\nReviewed By: javache\n\nDifferential Revision: D3392219\n\nfbshipit-source-id: ae372dfe9ceab7f7c2da69c731515a05eb3b020a","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/42a5568419fb1fea6ffdd59725f065949d799a7f"},{"sha":"1dc33b5f23640a60682ac879b9a3e94a4aa519d9","author":{"name":"Hedger Wang","email":"997d4010f1c98bf1d02cd1a42ab2ebf0bf5aa47e@fb.com"},"message":"Add example for composite navigation.\n\nReviewed By: hramos\n\nDifferential Revision: D3388314\n\nfbshipit-source-id: 7066363e03534e75ccdf8806db9ed395ee2163a4","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/1dc33b5f23640a60682ac879b9a3e94a4aa519d9"},{"sha":"bc7ec03670c0b61cf667f67bdeebf6877fa87c5a","author":{"name":"Alexander Blom","email":"c5cc088492f67dea609e2bf3debef70f3d4a1886@instagram.com"},"message":"Add better markers for getConfig\n\nReviewed By: astreet\n\nDifferential Revision: D3358278\n\nfbshipit-source-id: 16668cd33a42a120c2de88be4cb4a1c8d0d5a13c","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/bc7ec03670c0b61cf667f67bdeebf6877fa87c5a"},{"sha":"1fce89176b2b87ea1914f94cf036b06a3176c4c1","author":{"name":"Ben Nham","email":"afb7bae3e313b0be3ab05e8c07d27bb8641ac78d@fb.com"},"message":"Explicitly set default background color in RCTTextView\n\nSummary:\nRCTShadowText currently explicitly defaults to black text color:\n\nhttps://github.com/facebook/react-native/blob/d46ac11/Libraries/Text/RCTShadowText.m#L204\n\nHowever, the UITextView used by RCTTextInput doesn't explicitly default to black text color.\n\nThis causes issues when RCTTextInput is in rich text editing mode (i.e. when the <TextInput> element uses child <Text> nodes to provide extra styling info) and the client doesn't provide us with any explicit color info. In this case, the following series of badness occurs:\n\n1. -[UITextView attributedText] will return an attributed string without the NSColor property set.\n2. -[RCTShadowText attributedString] will return an attributed string with NSColor equal to blackColor.\n3. The `[_textView.attributedText isEqualToAttributedString:_pendingAttributedText]` check in -performPendingTextUpdate will fail and causes -[UITextView setText:] to be called.\n4. -setText: clears the marked text range in the text view, which breaks multi-character autocomplete (e.g. QWERTY input methods for CJK languages).\n\nThe easiest fix for now is to just make sure RCTUITextView and RCTShadowText default to the same text color.\n\nReviewed By: nicklockwood\n\nDifferential Revision: D3368726\n\nfbshipit-source-id: a92cb188c60bac80d963af6b1f2a09f27ae084f5","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/1fce89176b2b87ea1914f94cf036b06a3176c4c1"},{"sha":"8d038572f3c42033cfcc7a7901eea0ff75bbc32a","author":{"name":"Sokovikov","email":"5befc93b1b606baa4dd7f5ed5f603e6ab6e2ad37@yandex.ru"},"message":"show stacktrace in yellowbox\n\nSummary:\ninstead of #7030\n\n<img src=\"https://cloud.githubusercontent.com/assets/1488195/15109209/f31dbbbc-15e2-11e6-80b0-99aeea7eb630.gif\"\" width=\"300\" />\nCloses https://github.com/facebook/react-native/pull/7459\n\nDifferential Revision: D3282147\n\nPulled By: frantic\n\nfbshipit-source-id: cd79b729685047c303945e83d0672ca1671e2cca","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/8d038572f3c42033cfcc7a7901eea0ff75bbc32a"},{"sha":"2e7a536aba17c49974d98ce2aeea274047ab24c2","author":{"name":"Hedger Wang","email":"997d4010f1c98bf1d02cd1a42ab2ebf0bf5aa47e@fb.com"},"message":"Unbreak Image.ios.js\n\nSummary: Don't pass `null` as default empty uri. Use `undefined` instead.\n\nDifferential Revision: D3393211\n\nfbshipit-source-id: ac7cd385aa7f2196bc0743b8679dd2c94be4108b","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/2e7a536aba17c49974d98ce2aeea274047ab24c2"},{"sha":"2fd537c55dddd2a7e9906add5f6281b0444cc9b6","author":{"name":"Geoff Lawson","email":"b939a503a5bbef020883804c83e85e70de4d3333@build.com"},"message":"Incorrect import reference of emptyFunction causes error when importi…\n\nSummary:\nExperimental component SwipeableListView fails to import due to incorrect import reference.  Followed example use of import of emptyFunction found in https://github.com/facebook/react-native/blob/master/Libraries/Components/TextInput/TextInput.js#L31\nCloses https://github.com/facebook/react-native/pull/7954\n\nDifferential Revision: D3394202\n\nfbshipit-source-id: db8ddc9d9635878f0ce1fb969ef6c6e3c27d63f3","distinct":true,"url":"https://api.github.com/repos/celalnsa/react-native/commits/2fd537c55dddd2a7e9906add5f6281b0444cc9b6"}]}
{"actor":{"display_login":"celalnsa"}}