Export types instead of modules for testing purposes

Our end-to-end test as well as the terminal UI example both peek into a
bunch of program internals for their reuse. So far this was made
possible by exposing the containing modules publicly. That is an overly
broad exposure and it leaks the internal structure of the program to the
"outside".
This change takes a different route, exposing only the types strictly
necessary to be exposed, but keeping their containing modules private.

examples/with-test-data.rs

@@ -7,11 +7,11 @@ use std::io::stdout;
 
 use anyhow::Result;
 
-use notnow::cap::DirCap;
 use notnow::run_prog;
-use notnow::state::TaskState;
-use notnow::state::UiConfig;
 use notnow::test::default_tasks_and_tags;
+use notnow::DirCap;
+use notnow::TaskState;
+use notnow::UiConfig;
 
 use tempfile::TempDir;
 

src/lib.rs

@@ -60,22 +60,26 @@
 
 //! A terminal based task management application.
 
-pub mod cap;
+mod cap;
 mod colors;
 mod db;
 mod id;
 mod ops;
 mod position;
 mod resize;
 mod ser;
-pub mod state;
+mod state;
 mod tags;
 mod tasks;
 #[cfg(any(test, feature = "test"))]
 pub mod test;
 mod ui;
 mod view;
 
+pub use crate::cap::DirCap;
+pub use crate::state::TaskState;
+pub use crate::state::UiConfig;
+
 use std::env::args_os;
 use std::ffi::OsString;
 use std::fs::create_dir_all;
@@ -116,10 +120,7 @@ use tokio::runtime::Builder;
 use gui::Renderer;
 use gui::Ui;
 
-use crate::cap::DirCap;
 use crate::resize::receive_window_resizes;
-use crate::state::TaskState;
-use crate::state::UiConfig;
 use crate::ui::Event as UiEvent;
 use crate::ui::Message;
 use crate::ui::Renderer as TermUiRenderer;

tests/test.rs

@@ -4,11 +4,11 @@
 use std::ffi::OsString;
 use std::io::sink;
 
-use notnow::cap::DirCap;
 use notnow::run_prog;
-use notnow::state::TaskState;
-use notnow::state::UiConfig;
 use notnow::test::default_tasks_and_tags;
+use notnow::DirCap;
+use notnow::TaskState;
+use notnow::UiConfig;
 
 use tempfile::TempDir;