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
Working with onRemove: (value: React.ReactNode, index: number) is inconvenient under TypeScript's strict compiler options. Even when the values prop is string[], you are either forced to type cast the removed value to string or use the index parameter to index into your values array. We should make the simple case easier to work with, either with a new component API or changing the existing component to be parameterized by its data type <T>.
The text was updated successfully, but these errors were encountered:
This is not applicable under TypeScript's strict compilation modes, so we should not recommend the implicit type coercion. #4390 tracks improving the API usability for string-only TagInputs.
Working with
onRemove: (value: React.ReactNode, index: number)
is inconvenient under TypeScript's strict compiler options. Even when thevalues
prop isstring[]
, you are either forced to type cast the removed value tostring
or use theindex
parameter to index into your values array. We should make the simple case easier to work with, either with a new component API or changing the existing component to be parameterized by its data type<T>
.The text was updated successfully, but these errors were encountered: