Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate top level ReactInstanceManager changes #30

Closed
wants to merge 42 commits into from

Conversation

erikschlegel
Copy link
Contributor

No description provided.

erikschlegel and others added 11 commits December 23, 2015 09:32
In addition to some minor cosmetic changes, this changeset also fixes up the IReactPackage interface and more closely mimics the way IReactPackage is used in the ReactInstanceManagerImpl in ReactAndroid to support loading multiple packages into one NativeModuleRegistry and one JavaScriptModulesConfig.
@review-ninja
Copy link

ReviewNinja

@@ -3,6 +3,7 @@
using System;
using System.Collections.Generic;
using System.Threading.Tasks;
using ReactNative.Bridge.Queue;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This namespace needs to be sorted.

erikschlegel and others added 27 commits December 26, 2015 17:53
Also adds two-phase initialization of the ChakraJavaScriptExecutor so the instance can be created off the JavaScript thread.

Also fixes a bug with the UIManagerModule constants and adds unit tests for custom event types and constant overloading by view managers.

Also adds a simple base interface (IViewManager) for view managers to hold names and constants.
Fixes #62 - Adds EventDispatcher
Adds various other stubs that we will need to implement as we move forward.
…ttribute

Adding attributes to match the Java annotations for @ReactProp and @ReactPropGroup, along with unit tests.
Remaining TODOs surrounding layout, popup menu, measurement, etc.
Towards #70 - Adds implementation for NativeViewHierarchyManager
…Currently working with JFox to help with debugging the issue
The ReactShadowNode implementation derives from CSSNode. Rather than port over the entire csslayout project that Facebook created, we're using a compiled binary (checked in) from https://github.com/pragmatrix/css-layout. We needed to hook into the `dirty` method, so there is one small modification to the library.
rozele pushed a commit that referenced this pull request Jun 21, 2019
Remove "not used in production" warning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants