[Enhancement] Add menuRenderer prop to support windowing for large lists

[bvaughn]

I believe this PR resolves the following open issues: #554, #674, #739, #771, #807.

This PR adds support for windowing libraries like react-virtualized to be used to render large lists of options. It is similar to the approach mentioned in PR #763 but it avoids creating all of the menu options when rendering and so it performs better.

The size of the PR is mostly due to the fact that it contains a JSON data file of the largest 1,000 cities in Europe (used to demonstrate custom menu windowing). The actual changes to the Select component were very minimal (~40 new lines).

This change-set includes:

• New renderMenu prop added to Select component.
• New tests added to test/Select-test.js for new property. (Previous tests all pass.)
• README updated to mention newly added property.
• Example page updated to demonstrate new property as well. (Live demo of this functionality can be seen here, under "World's Largest Cities" header.

Note that react-virtualized was added to the devDependencies section (not dependencies) so it could be used in the example to demonstrate a more efficient way of rendering select menus with large amounts of data.

If this PR gets merged, or one like it, I plan to release a small adapter library with a single HOC that provides the react-virtualized drop-down menu automatically and passes through other props to Select. (In other words, I'm happy to take over the ownership of the feature.)

[coveralls]

Changes Unknown when pulling 03b3f00 on bvaughn:master into * on JedWatson:master*.

[coveralls]

Changes Unknown when pulling 071ae88 on bvaughn:master into * on JedWatson:master*.

[coveralls]

Changes Unknown when pulling 143bd64 on bvaughn:master into * on JedWatson:master*.

[coveralls]

Changes Unknown when pulling 9e11ce9 on bvaughn:master into * on JedWatson:master*.

[cloudkite]

maybe menuRenderer would be better choice since it follows existing naming convention of optionRenderer?

[bvaughn]

Renamed. Thanks for the suggestion.

[cloudkite]

Nice work! 👍

I think it would be good idea not to include examples/dist and lib folders in the PR, makes it alot more readable

[bvaughn]

Truth. I wanted a live demo to point out so I had to push them to my fork. But maybe I'll clean up this PR and use another branch for the demo. Thanks for the input :)

[coveralls]

Changes Unknown when pulling 3b591bf on bvaughn:master into * on JedWatson:master*.

[coveralls]

Changes Unknown when pulling 3b591bf on bvaughn:master into * on JedWatson:master*.

[bvaughn]

Okay. Dist files have all been removed. Only large files still around are the example cities list.

[coveralls]

Changes Unknown when pulling 9e18d92 on bvaughn:master into * on JedWatson:master*.

[coveralls]

Changes Unknown when pulling a64c43f on bvaughn:master into * on JedWatson:master*.

[coveralls]

Changes Unknown when pulling a64c43f on bvaughn:master into * on JedWatson:master*.

[JedWatson]

This looks fantastic @bvaughn! Thanks for the PR, and for owning the feature :)

[naveg]

This is great. It seems like it should be possible to use react-tether in the menuRenderer function, but I'm having trouble getting that to work. Problem is that I think the tether target should be the Select-control component, which isn't available here. Only thing I can think of it to add a dependency on react-tether and wrap the Select-control and menu in a TetherComponent, which we definitely don't want. Any ideas?

[Craga89]

👍 to this. This is way more flexible than the menuComponent PR I made, great job @bvaughn! I'd love to see this merged so we can translate our current implementation over!