react-native-macos/React
Martin Kralik 7f2b72528e RCTEvent protocol changes (3/7)
Summary:
I want to use the `RCTEvent` protocol for touch events as well. That's why I'm removing not very well defined `body` property and replacing it with `arguments` method, which will return an array that will be passed directly to the js call.
I think this makes sense because there is no unified arguments format for all events and and the called  js method (`moduleDotMethod`) is already event specific.
This way touch events and scroll events can result in calling a completely different js function with a completely different arguments (what they indeed currently do).

public
___
//This diff is part of a larger stack. For high level overview what's going on jump to D2884593.//

Reviewed By: nicklockwood

Differential Revision: D2884590

fb-gh-sync-id: 2c1885c3414e255d8572c0fbbbfe62a23d94dd06
2016-02-03 05:23:50 -08:00
..
Base RCTEvent protocol changes (3/7) 2016-02-03 05:23:50 -08:00
Executors Hot Loading Sourcemaps 2016-01-27 14:55:36 -08:00
Layout updated css-layout and fixed callsites 2015-12-21 10:18:41 -08:00
Modules Hot Loading Indicators 2016-02-01 12:42:33 -08:00
Profiler Handle bad JSON data without crashing 2016-01-26 06:13:29 -08:00
React.xcodeproj Refactor hot loading implementation on iOS 2016-01-04 10:40:32 -08:00
Views RCTEvent protocol changes (3/7) 2016-02-03 05:23:50 -08:00