Summary:
Never really liked this code. Before this change, calls to connect were blocking.
Because of this, we had to make use of promises and a bit of really not that good-looking code.
So, this change makes connect non-blocking meaning that we make full use of our event handler.
These changes contain:
- CSR is not getting generated after each failed attempt.
- Connect is no longer blocking.
- Do not report events via the handler when explicitly disconnecting.
Reviewed By: jknoxville
Differential Revision: D46853228
fbshipit-source-id: 00e6a9c7c039a756175fe14982959e078d92bacb
Summary:
Last diff in the the RNW saga.
This change creates the necessary bridgings between the module and the plugin.
With this in place, JS plugins can be written and used. Also, we have a fully functional RNW sample app.
Reviewed By: aigoncharov
Differential Revision: D39087480
fbshipit-source-id: f4fde404716aa619a64553ffa556d060f49c0ac7
Summary:
^
This diff brings most things together and can be considered the test platform for RNW.
With this, Flipper client gets initialised and started.
This means the application connects and is ready for debugging.
Reviewed By: antonk52
Differential Revision: D39054912
fbshipit-source-id: 94397f6a72b1e9d9c0f2f3efaf9967be525076cd
Summary: Introduces a Scheduler implementation using ReactDispatcher. The scheduler is/will be used by the FlipperConnectionManager as to serialise socket operations in it.
Reviewed By: antonk52
Differential Revision: D39053301
fbshipit-source-id: 5bc2d68a753ec4be3e28533b4c29e2d6ff6d8ba0
Summary:
This change is the direct results of doing the following:
npx react-native-windows-init --overwrite
Notes: ignore the format warnings below. In this case, the ordering of includes does matter. Missing license is for auto-generated files, so ignore too.
Reviewed By: aigoncharov
Differential Revision: D36775215
fbshipit-source-id: 1cd00ff2bfc258c8505e97dcdbd9cb4365c4acfb
Summary:
Nothing interesting here, just adding necessary sources from Flipper into the VS Studio solution.
As a consequence, some warnings had to be turned off as otherwise they're treated as errors and the solution doesn't build.
Reviewed By: passy
Differential Revision: D36760242
fbshipit-source-id: 2f5e615f8a465554dd35c245756f94bcace6e34a
Summary:
This change brings in Folly and Boost into our solution.
Boost is resolved with NuGet. Folly is resolved by re-using the RNW integration.
For reference:
Flipper depends on Folly. Folly depends on a few things:
- Boost
- FMT
- Glog
- Double-Conversion
Folly from RNW uses some stubs to resolve fmt, glog, and double-conversion. That's OK.
Only Boost needs resolving.
On Visual Studio, we can use the following package managers: NuGet and vcpkg.
Boost can be resolved using either.
Using NuGet as otherwise vcpkg needs to be run locally by anybody wanting to build the solution. NuGet makes things easier.
Reviewed By: aigoncharov
Differential Revision: D36759384
fbshipit-source-id: 31a9a398ce5c5dc2f3def02689ae4bb8c42fbb99
Summary:
This change adds the template for a RNW module to the existing react-native flipper project.
Basically, the changes in this diff are the product of executing the react-native-windows init for the existing library.
See:
https://microsoft.github.io/react-native-windows/docs/getting-startedhttps://microsoft.github.io/react-native-windows/docs/native-modules-setup
Notes:
There's some auto-generated module code contained in this change: ReactNativeModule (.h/.cpp)
allow-large-files
Reviewed By: passy
Differential Revision: D36751772
fbshipit-source-id: 41207bedb00ea147883f6d13336ed6c1da4454d7
