@JulioCotta@Zhuinden@JimSproch@Alex_Zhukovich @assisted @inject Whether or not you should do this is highly contextual. We inject markwon in this way because it’s considered a UI concern and tedious to pass in as an argument everywhere that needs it.
@JulioCotta@Zhuinden@JimSproch@Alex_Zhukovich @assisted @inject You can’t but LocalContext provider can be used to grab a context - if you’re using hilt you can create an EntryPoint to access the dagger graph (other DI frameworks provide something similar given a context, hilt is just what I’m most familiar with)
Anyone explore adding a CompositionLocal for "enabled"? This feels like a convenient way to make an entire Composable hierarchy disabled, but not sure how well it'll work in practice 🤔
I feel like I solve so many technical problems with cmd + shift + f/livegrep.
“Hmm this isn’t working how I expect, who else is using this” - sounds really simple but in my experience it isn’t people’s first thought
Sometime in the far, far future: humans have expanded across the galaxy, met intelligent life, mastered fission, and this check reaches the milestone of being updated to 19..Int.MAX_VALUE
It's 2022 and Samsung still has custom static view fields added to the Android framework.
API 19 to API 31. Can't wait to update this again in API 32..
https://t.co/ug6kcnCpOg
#leakItLikeItsHot#AndroidDev