Updated to 09. I cannot BELIEVE the TextField stuf...
# composec
codeslubber
04/15/2020, 9:57 PMUpdated 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….
🙃 1
i
ianrumac
04/15/2020, 10:30 PMwell, it is a dev build after all 🙂
☝️ 9
c
codeslubber
04/15/2020, 10:35 PMreally 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?
z
Zach Klippenstein (he/him) [MOD]
04/15/2020, 10:40 PMThe release notes always link to the full commit history since the last release, might be something in there?
👍🏻 1
c
codeslubber
04/15/2020, 10:44 PMLooks like they added a class called
FilledTextFieldcodeslubber
04/15/2020, 10:45 PMThe issue was
TextFieldTextFieldValuej
jim
04/15/2020, 11:12 PMYou peaked my curiosity so I had to go look it up 😏
s
Siyamed
04/15/2020, 11:13 PMwe forgot to add release notes to commit message 😕
Siyamed
04/15/2020, 11:13 PMI feel responsible for this and sorry for the trouble @codeslubber
👍🏻 1
j
jim
04/15/2020, 11:14 PMThis 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
FilledTextFieldMaterialTextField.kt👌 2
c
codeslubber
04/16/2020, 12:39 AMGuys 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🙂 1
v
Vlad Gorbunov
04/16/2020, 6:48 PMtho i must admit
TextFieldTextFieldValueTextFieldSample7 Views