@sylvie_b3@Zhuinden@androiddevnotes Some would say manual classes construction. I find it ridiculous since Retrofit itself is as far from plain network requests as Hilt from manual constructors calls.
Alternately, realize that Hilt and Koin don't really do much other than that you have to "type a little less code".
Though if you use Dagger enough, you find that the "less code" is actually more code. If you ever try to Ctrl+Shift+F and half the finds are Modules, you get it...
I love @GitKraken but it's ridiculous that it crashes if a changed file has "constructor" or "tostring" substring in the name. And the only way to resolve that is to use some other client to commit changes. What a shame.
@oleg_nenashev@androiddevnotes@gradle Sorry, how is that related to transitive dependencies verification? I’m really interested in the topic but see no direct connection.
@igorwojda Konsist's docs state that there is no way to generate tests dynamically in JUnit 4. I think that's not true - there are Parametrized tests which do exactly that. Am I missing something? https://t.co/CSy4Pzeyqk
Пытался сгенерировать диаграмму классов на основе кода, чтобы проанализировать связи. Потратил пару часов, но хорошего инструмента не нашлось. Решил изначальную задачу за 10 минут вручную прошерстив файлы.
And with a pinch of StateFlow you can observe changes in that cache. Yeah, get() now looks weird, since we first call .value of StateFlow itself and then call .vall of the wrapped Lazy.
@Zhuinden@androiddevnotes I can totally understand that. Everything comes with its drawbacks. That's why I'm not ready to rely on Hilt or Anvil. Pure Dagger gives more control and clarity.