Skip to content

Conversation

@sophiebits
Copy link
Collaborator

Fixes #2386.

Test Plan: jest

Reviewers: @sebmarkbage

@sophiebits sophiebits added this to the 0.12 milestone Oct 21, 2014
Copy link
Collaborator

Choose a reason for hiding this comment

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

"...or undefined"?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

well we don't really want to encourage people to leave off keys… but I can say that. :)

@sebmarkbage
Copy link
Collaborator

spyOn doesn't allow you to revert back to the original if you want to start failing again but it's fine.

@sophiebits
Copy link
Collaborator Author

Lots of other tests in the same file use spyOn…

@sebmarkbage
Copy link
Collaborator

I guess spyOn doesn't callthrough by default so it should work. And I guess you can revert it. Just a sucky API.

@sebmarkbage
Copy link
Collaborator

@spicyj feel free to merge in any of yours that are accepted for 0.12. Right, @zpao ?

@sebmarkbage
Copy link
Collaborator

Unless they fail CI like this one...

@sophiebits
Copy link
Collaborator Author

@sebmarkbage Transient failure – retried and it works.

@sebmarkbage
Copy link
Collaborator

cool. mergeit

sophiebits added a commit that referenced this pull request Oct 21, 2014
Support but warn on key={null}
@sophiebits sophiebits merged commit 631b6a0 into facebook:master Oct 21, 2014
@zpao
Copy link
Member

zpao commented Oct 21, 2014

feel free to merge in any of yours that are accepted for 0.12.

As long as the milestone is 0.12, yes. Then once we cut we can apply that rule to master as well.

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.

Regression in null key handling in 0.12 (possibly intentional)

3 participants