Updated to 09. I cannot BELIEVE the TextField stuff is broken again, and there’s no mention of it in the release notes. Just feels like utterly pointless thrashing….

well, it is a dev build after all 🙂

really helpful guys, thanks, of course I understand things get broken, I am complaining about the fact that this changed, I updated everything, and it’s changed again, and it didn’t merit a mention in the notes?

The release notes always link to the full commit history since the last release, might be something in there?

Looks like they added a class called

FilledTextField

?

You peaked my curiosity so I had to go look it up 😏

we forgot to add release notes to commit message 😕

This decision was made because the expectation is that a casual developer won't use this API in framework and will instead use the Material TextField API (or an API provided by their favorite design library). For this reason, the expected customer of this API is a library author implementing a custom TextField, so the String overload is not particularly useful for them. If you look at the

FilledTextField

in

MaterialTextField.kt

, that provides a convenient String overload and is the API you will want to use.

Guys hey sorry to sound like such a baby. I am perfectly happy with whatever changes, it’s just hilarious that I was on here after 7 or 8 discussing with a G dev, and was urged to use String instead of

TextFieldValue

. Super excited 9 dropped, and was just kind of dumbfounded when that broke. Thanks for the quick response!

tho i must admit

TextField

with

TextFieldValue

behaves really strange 😄 i am a bit frustrated now, tried to go look into

TextFieldSample

and found out there is no sample package in there 😄 😄