Sync code with fbjs to fix a bug

[realityking]

I tried using this package in create-react-context (see jamiebuilds/create-react-context#22) and discovered a bug compared to fbjs.

This line would not work correctly:

warning(
  (changedBits & MAX_SIGNED_31_BIT_INT) === changedBits,
  'calculateChangedBits: Expected the return value to be a ' +
  '31-bit integer. Instead received: %s',
  changedBits
);

Since it did work in fbjs I simply resented the code. I also removed to react-isms in follow-up commits.

[TravisBuddy]

Hey @realityking,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

[realityking]

Build failure will be fixed with #31

[BerkeleyTrue]

Why won't this code work? What's the value of changedBits and MAX_SIGNED_31_BIT_INT?

[realityking]

@BerkeleyTrue I didn't fully debug it. My first attempt was simply to check if the upstream implementation in fbjs had the same issue. Since it doesn't, is it really worth understanding why they behave differently?

[BerkeleyTrue]

It may have been a bug introduced a couple of months ago. A fix has been released as https://github.com/BerkeleyTrue/warning/releases/tag/v4.0.3

Happy Coding

[realityking]

@BerkeleyTrue That did indeed fix things. Thank you!