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

Copy React ART tests and add hacks to fix them #6775

Merged
merged 3 commits into from
May 24, 2016

Conversation

sophiebits
Copy link
Collaborator

This helps us make sure we don't break React ART in a minor or patch release. The idea is to not change these files when making minor or patch changes. Copied directly from react-art with requires fixed. (I also picked a different haste name just in case.)

Then I fixed the tests.

@sophiebits
Copy link
Collaborator Author

@facebook/react-core This is kinda icky. My native/host rename mucked this up (getNativeNode) but the devtools warns about missing debug IDs too before this change. We can't really change React ART because we have no way to guarantee that people aren't using React ART v15 with React 15.1.

@sophiebits
Copy link
Collaborator Author

Well, apparently we haven't published React ART 15.0. But the point stands, I think.

@sophiebits
Copy link
Collaborator Author

Can we just actually ship ReactART's source inside the react npm package and then we won't have to worry?

@ghost
Copy link

ghost commented May 15, 2016

@spicyj updated the pull request.

@zpao
Copy link
Member

zpao commented May 16, 2016

Can we just actually ship ReactART's source inside the react npm package and then we won't have to worry?

Isn't that the opposite of what we want to do with renderers?

@sophiebits
Copy link
Collaborator Author

Ehh… React ART is weird because it isn't its own environment so we can't make things completely separate. Unlike React DOM and React Native where it's okay if they have different versions (and we don't want them to share any state or code). Maybe we can try to make React ART more independent (and that might be a good idea anyway) but we're not set up for that right now.

@sebmarkbage
Copy link
Collaborator

ART doesn't depend on shared state other than owner and current context.

Just copying all the files from React to ART should be sufficient too.

The question is, if we keep going in the opposite direction of decoupling, when will we ever get to a decoupled state? What spin off effects will we get from doing this?

On May 15, 2016, at 10:27 PM, Ben Alpert notifications@github.com wrote:

Ehh… React ART is weird because it isn't its own environment so we can't make things completely separate. Unlike React DOM and React Native where it's okay if they have different versions (and we don't want them to share any state or code). Maybe we can try to make React ART more independent (and that might be a good idea anyway) but we're not set up for that right now.


You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub

@sophiebits
Copy link
Collaborator Author

Okay, we don't have to merge them. Does this PR look good though? I want to be able to test against React ART even if we consider them decoupled.

// We renamed this. Allow the old name for compat. :(
if (!instance.getHostNode) {
instance.getHostNode = instance.getNativeNode;
}
Copy link
Member

Choose a reason for hiding this comment

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

Since we didn't ship ReactART 15 yet… we could just make it depend on 15.1 and not support 15.0.

This helps us make sure we don't break React ART in a minor or patch release. The idea is to not change these files when making minor or patch changes. Copied directly from react-art with requires fixed. (I also picked a different haste name just in case.)
@facebook-github-bot
Copy link

@spicyj updated the pull request.

@zpao zpao added this to the 15-next milestone Jun 1, 2016
zpao pushed a commit to zpao/react that referenced this pull request Jun 8, 2016
Copy React ART tests and add hacks to fix them
(cherry picked from commit 531a6b3)
zpao pushed a commit that referenced this pull request Jun 14, 2016
Copy React ART tests and add hacks to fix them
(cherry picked from commit 531a6b3)
@zpao zpao modified the milestones: 15-next, 15.2.0 Jun 14, 2016
@zpao zpao modified the milestones: 15.2.0, 15-next Jun 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants