Weird typings for onChange badly needs a refactor.

These types are silly:

const [ selectedValues, setSelectedValues ] = useState<OptionsType<OptionType>>([])

const handleChange = (values: OptionsType<OptionType>, actionMeta: ActionMeta<OptionType>) => {
  // do something
}

Not only are these types unintuitive in of themselves, but they are also not well explained neither in the docs nor elsewhere online. Problem solving these types has costed me a huge amount of time. As much as I would love to replace these types with “any”, I’m working with a strict linter that doesn’t allow such things. I seriously look forward to the day when I can just dip in-and-out of a visual editor like Webflow to do UI, but since visual editors don’t yet integrate with complex code bases, I’m stuck dealing with silly types likes these.

Please consider making it a priority to both refactor these ugly types and to update the docs to make it easier to apply them.

[ebonow]

This was a complete refactoring of Flow to TypeScript. We are happy to consider any updates to the types, but these conversations would likely be a better fit for the Discussions area as would any topic regarding a change from value representing a String or Number instead of an Object.

Again this rewrite was based on the intention of creating compatible code. The next major version would likely be a bit more opinionated with breaking changes (like the one mentioned above abut changing the type of the value), so it’s one that we would happily address if it were a popular topic in the Discussions area and made sense to do so.

Suggestions are far more helpful than judgements.

[Methuselah96]

How would you suggest we refactor the types? Feel free to suggest better types and/or open a PR with the changes.

We’re working on improving the documentation website, so hopefully once that’s done there will be opportunity to add some documentation for using the types. Feel free to create a PR for adding that documentation now as well though.