`onInputChange` documentation does not reflect behavior
Documentation of the onInputChange return type does not reflect its actual return type, and what can be done with it
In the doc, return type is void
But while implementing my use-case, I found out that this is actually possible using the return type of this same method, for example here. This is also shown in this example in this same repository.
It seems to me that the documentation should be aligned with the real return value of this method, which is string | undefined AFAIK
WDYT? If you agree with this, I am eager to create a PR for it.
Wow, completly forgot about this, I'll check and see if that's a quick fix
That's not a quick fix
- Multiple locations need to account for the new type
- The magical-types library used in this project omits the
undefinedfromstring | undefined
Unfortunately, I don't have the time at the moment to fix this now. I still think this is an issue and should be fixed, so I'll keep the issue open for now.