Alex Krupa

Shouldn't the file's name be `LayoutInflater.kt` instead of `LayoutInflator.kt`?

Any update on this? I think a sealed class approach would be alright, e.g. ```kotlin sealed class Size { object WrapContent : Size() object MatchParent : Size() class Exact(@Px size:...

Here's a similar repro case to @ferinagy's one, but mocking a subclass instead. ```kotlin abstract class Superclass { open suspend fun wait(): Int = TODO() } class Subclass : Superclass()...

I was blocked by this when trying to integrate Hyperion into a project with [`moshi-kotlin-codegen`](https://github.com/square/moshi#codegen) which also uses AutoService. I figured one other, slightly dirty solution would be to use...

Correct, Hyperion launches its crash activity in a separate `:crash` process, which causes `Application` class recreation. You can work around this issue by initializing your dependencies in that same process....

Personally, I wouldn't use errors or I'd lower the severity right after the first failure. 🙈 It only applies to `severity = Error` though, right? It can still be an...

Correct. I want the safe builder without adding pulled features to the inspector tab. I could imagine fine-grained variants of `dependency` API that would let me do that… >a single...

> I'm open to the UI design changes if you have a good idea on how to handle dozens of flags. A [Chips](https://m3.material.io/components/chips/guidelines)-based filter UI seems like a good fit...

I'd see the UI as a flat list, with the filter chips on top. The filters could be collapsed by default to make space (e.g. single, scrollable line), but with...

12 tabs, so no. It's not a deal-breaker, but I'd personally prefer a flat list with sections (collapsible?). (I'm aware that I can achieve a flat list by combining factories.)