Does anyone know the rationale behind not exposing...
# composem
mattinger
02/03/2022, 3:54 PMDoes anyone know the rationale behind not exposing any semantic properties for text styles? All i seem to be able to validate is the text string, but not the font size, font family, etc….
t
tad
02/04/2022, 6:06 AMBecause semantic properties are primarily meant for accessibility services
m
mattinger
02/04/2022, 2:18 PM@tad That’s kind of the issue though. How else would you test things like that? There’s no actual view to access with discrete properties. Semantics are the only way to test anything conditions in compose. Im not directly looking to test things like color. But i do have custom properties to test. I have a button which has a “tone” property that when combined with a “variant” and “size” affect colors, padding, etc…. I don’t necessarily need to test the colors and fonts directly, but i did add semantic properties for these 3 attributes so i can ensure that a given UI is putting the right type of button in the right slot.
mattinger
02/04/2022, 2:19 PMI’m just wishing that more things were exposed in the semantic properties to validate this sort of stuff.
mattinger
02/04/2022, 2:20 PMTo be honest, it’s a big miss in my opinion to be able to create a text field like this in your UI:
Copy code
Text(..., style=MaterialTheme.typography.body1)t
tad
02/04/2022, 5:54 PMYou can set tags, and it's not hard to create semantics keys
tad
02/04/2022, 5:55 PMBut at some point you have to trust that the Composable did the right thing with the arguments you provided to it
tad
02/04/2022, 5:55 PMOtherwise you're testing the framework, and not your app