Where can downshift be improved?

Hey friends! I’m looking for feedback. Where can downshift be improved? This is an open-ended question and I’m looking for ideas. How can we improve the docs? What can we improve about the API? How can the implementation be improved?

A few ideas I have:

1. A legit website with an easier way to add or contribute to examples (I have some ideas here… Maybe it could just be a repo that could be loaded into codesandbox which we’d publish via netlify… Very easy to contribute to via codesandbox’s github integration).
2. Some auxiliary component packages that implement a simpler, more opinionated and intrinsically useful autocomplete/dropdown/etc. on top of the downshift implementation.
3. Release 2.0.0 which will remove the breakingChanges prop and also bring improved support for TypeScript and Flow.

Any other ideas? Remember that downshift itself is intended to be extremely flexible, so if what you’re looking for is a simpler API, then consider whether you could build a component on top of downshift that exposes that API. If that’s possible then let’s do it and publish that!

[kentcdodds]

Another thing we should consider is improving composition so we don’t have to have so much conditional logic. Perhaps create a base component that has the common logic, then expose dom and native-specific components on top of that for the differences… That may make things more complex though… Not less…

[kentcdodds]

Going to go ahead and close this one now 😃