Fix toOrderedMap, toOrderedSet Flow annotations

[rvikmanis]

No description provided.

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[marudor]

Actually this will introduce some problems.
Thats why I left them as Map/Set for now.
But the main signatures for Maps/Set is the same for Ordered.
So it shouldn't be a problem to leave them.

[mitermayer]

I also hit on this problem

@marudor on the project https://github.com/facebook/draft-js with immutable '3.7.4' the flow build works just fine.

But since the dependency on the package.json is set as '^0.7.4' the version that gets installed via npm install is ''3.8.1" which is incompatible and fails

[lacker]

So #878 refactored the flow types and also added tests for them. Would you mind updating this PR to merge those changes in, and also add a test that catches this? Thanks!

[howardjing]

I fixed the merge conflicts in this PR / added tests / updated annotations for OrderedSet and OrderedMap in this PR: #1027

[kozlitinaelja]

Hi there. I am starting handling backlog. I know it is been a while since you've submitted PR, sorry for such delay. The are some conflicts. Could you, please, rebase? 😅

[howardjing]

@kozlitinaelja #1027 is merged into master, which is a superset of this PR. I think this PR can be closed.