New name for library and base package
Closed this issue · 0 comments
RBusarow commented
"DispatcherProvider" isn't a very good name. For the interface, it's nice and descriptive, and a fairly common name for what it does, so I'm okay with leaving that alone.
As a library, though, it feels too descriptive to the point of being limiting. I would like to add functionality to the library with more modules and artifacts, where this new content is related to but definition not core to the functionality of DispatcherProvider
.
I've been using the name dispatch
as a base package for a few days, and I more or less like it.
The resultant package structure would look something like this:
import | description |
---|---|
dispatch.core.* | Core functionality, naturally |
dispatch.core.test.* | core testing functionality |
dispatch.extensions.* | essentially ktx for coroutines |
dispatch.core.test.android.* | IdlingDispatcher + dispatch.core.test |
dispatch.android.* (runtime artifact) | fork of androidx.lifecycle.runtime but more extensible and without the leaky pausing dispatcher |
dispatch.android.* (viewModel artifact) | fork of androidx.lifecycle.viewmodel but more extensible |