Dominic Zirbel

I'm able to reproduce the tests failing the build locally (had wondered if it was something about my local environment before pushing), but I'm not sure how to fix them...

> > It's possible the general assertFails{} calls in unit tests should be replaced with a form that also checks the throwable type, to avoid this issue elsewhere. > >...

What might be the most useful for my project - and what I believe most Android plugins do as well - is expose variant-specific versions of the task, like `projectHealthDebug`...

My 2c is that the current configuration management works well overall, and with the addition of exhaustive verification has been pretty much all I could ask for. I appreciate the...

That could work; the main use case I have is as part of a CI process that checks the configuration file is exhaustive - such a task which adds missing...

A near-ideal solution might be to have `compile-snippet-tests` be enabled by default when running a single test but not the entire test suite; that would make individual changes easier to...

> > be enabled by default when running a single test but not the entire test suite; that would make individual changes easier to test with minimal impact and wouldn't...

Yeah, I agree it can be confusing... on the other hand, so is the current practice :shrug: Just brainstorming some ideas, here are a couple more: - create a new...

Small plug and another example for anyone still looking for an easy way to add dividers to context menus - I've created a simple library with support for material styling...

Sorry for the very late response - yes, adding `onKeyEvent { true }` does seem to fix the problem. I'm not sure why I was returning `false` in the example...