`max_length` and `valid_inputs` Support for `rio.TextInput`

[Sn3llius]

Description

Enhance the rio.TextInput component by adding support for two new features: max_length and valid_inputs. These features will provide greater control over the input data by restricting the length of the text and the valid characters or patterns users can input.

Suggested Solution

max_length should be pretty self explanatory. Should work analogue to . Default should be None

valid_inputs should take a string or Iterable[str], preventing other symbols for being put in. default should be string.printable

Alternatives

No response

Additional Context

No response

Related Issues/Pull Requests

No response

[mad-moo]

While I like the proposal in general, I'd argue for an alternate way of specifying what constitutes valid content - regex. This would allow for much more flexibility in what users can (and cannot!) enter.

This comes with challenges however, which is also the reason it doesn't exist yet:

• Users would expect to provide Python-style regex, but since evaluation would happen on the client, the regex pattern would be interpreted according to JavaScript's rules
• This wouldn't be as simple as just entering a regex of what the user can submit, and leaving it at that. This is because the user can provide intermediate text which isn't valid, but turns valid again after more characters are entered. For example, suppose the user wanted to enter a number. 1 would be valid. 1. wouldn't. But 1.0 would be. The regex would thus have to allow for these nonsensical intermediate values.

This needs discussion.