{"push_id":3053486558,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"5bd1db84f0d13339279a6f25b2ecfb089e3a9fb2","before":"ab07596f9f08b7c1044d8d7b2609064cb658c573","commits":[{"sha":"b2bb52f778c673b2446d9fc4fad961994b2f5a71","author":{"name":"Jordan Brown","email":"57d16066d8b967c0452feca26f2b8baa4c44175b@fb.com"},"message":"[react] Get rid of polymorphic type aliases in react hooks api\n\nSummary:\nPolymorphic type aliases have a known bug where they may cause unnecessary unification. This causes a [problem for the react hooks API types](https://flow.org/try/#0CYUwxgNghgTiAEAXAngBwQISgZwJZgGVEpEQBBMRXAewDsAeAgPngF54AKAtlggSngAfeAQDcAKFCRYCFOngARXNlQkwAC3pkW7Mj3gA3armASp0OEjQIAslGQAjEAGEIIKLQCqqAGK028AD8HBwCrCwAtrgAHiDAfKLw4uIA9CnwAHLUiPAArni0AOZW8lAQuDgg2JLgFggg0ajUMDkAZrm0lDT++SBEJCAAjIxMHOLwE-C4tLhUZf2kAFycofr8QiIANOPwfMsA2gSbK9zhIgLC62dGJgC6EqnpngXFcghlFdhVNdKWDU0teDtTpUOh5L4LEAAJhGY0mUxmcwgkOWITCvAuWx2e3gh2OShUak0WDwhGIpAooIYzCY9x28PEwK6YNI2EQqwA3jswHQ2biAI65EAwZCDY5fRAARSFIshg1uAV6cpCtFyEAgy0CHOErWo1GWqoiThgQgAvnwEjsJdLhchlRzdfr4ABmc0PCY82h8-aC21Q8UgKUyu3k6EK9hK0NQlVqjVBbVAvUG3JG4Vmi0SCbW4OQ6MOpMut3iU1AA).\n\nTo get around this, we can get rid of the type aliases until this bug is fixed. The lack of unification made one test have confusing behavior-- I have a comment inline explaining why it errored before and why it requires an explicit type argument to retain its behavior.\n\nReviewed By: samwgoldman\n\nDifferential Revision: D13083694\n\nfbshipit-source-id: 87fc6b37cfaba1d4659d71a3b47ace89ca1b4658","distinct":true,"url":"https://api.github.com/repos/SimenB/flow/commits/b2bb52f778c673b2446d9fc4fad961994b2f5a71"},{"sha":"495a1c000a5ded4cf68fa4073fdf37966717d91c","author":{"name":"Jordan Brown","email":"57d16066d8b967c0452feca26f2b8baa4c44175b@fb.com"},"message":"[react] rest param in function_component can be None\n\nSummary: There's probably no need for a rest param here, but we should make an err diff to confirm.\n\nReviewed By: samwgoldman\n\nDifferential Revision: D13042872\n\nfbshipit-source-id: 10e80a54748e95458c8a0efcd7810cf7f1563f3d","distinct":true,"url":"https://api.github.com/repos/SimenB/flow/commits/495a1c000a5ded4cf68fa4073fdf37966717d91c"},{"sha":"5bd1db84f0d13339279a6f25b2ecfb089e3a9fb2","author":{"name":"Jordan Brown","email":"57d16066d8b967c0452feca26f2b8baa4c44175b@fb.com"},"message":"Better error messages for long string literals being treated as strings\n\nSummary:\nString literals with size over a max configurable length are treated as strings. It's helpful to know\nthat your string literals are being treated as strings without literal information, as revealed\nby a recent question in our support group.\n\nReviewed By: gabelevi\n\nDifferential Revision: D13044732\n\nfbshipit-source-id: 068852199252302fae1bb699de2c97c8996045d1","distinct":true,"url":"https://api.github.com/repos/SimenB/flow/commits/5bd1db84f0d13339279a6f25b2ecfb089e3a9fb2"}]}
{"actor":{"display_login":"pull"}}