Hi @dokar3 !
I am using the new 0.7.2-alpha01 version referenced here #131, and the current implementation of rememberChipTextFieldState when configuration changes not keep rember the value, can be used the new retain API that allows to persist non-serializable data and resist to configuration changes. Maybe can be useful also to allow to use custom keys in the rememberChipTextFieldState API to have custom behaviors to recreate the state. I hope can be a useful tip! If for you is helpful can I try to open a PR
Hi @dokar3 !
I am using the new 0.7.2-alpha01 version referenced here #131, and the current implementation of
rememberChipTextFieldStatewhen configuration changes not keep rember the value, can be used the new retain API that allows to persist non-serializable data and resist to configuration changes. Maybe can be useful also to allow to use custom keys in therememberChipTextFieldStateAPI to have custom behaviors to recreate the state. I hope can be a useful tip! If for you is helpful can I try to open a PR