You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently using the beta TextInputGroup components for type ahead support in Cost Management and the HCS UI. This has been working fine until we discovered users can enter characters which our APIs don't support. For example, multiple trailing commas and ampersand characters need to be omitted from API requests.
We can parse these characters from the text input, but would like to have validation support. For example, it would be ideal to identify which characters are invalid. Currently, I don't see an easy way to apply the styling, icons, and help text provided by this "validated" example.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're currently using the beta
TextInputGroup
components for type ahead support in Cost Management and the HCS UI. This has been working fine until we discovered users can enter characters which our APIs don't support. For example, multiple trailing commas and ampersand characters need to be omitted from API requests.We can parse these characters from the text input, but would like to have validation support. For example, it would be ideal to identify which characters are invalid. Currently, I don't see an easy way to apply the styling, icons, and help text provided by this "validated" example.
Cost Management's type ahead component
Beta Was this translation helpful? Give feedback.
All reactions