Move the components into their own module

This makes the module tree more reflective of module use patterns. In
particular, it restores the condition that every top-level module is
used in top-level code, which was broken by the addition of the
`test_assembly_chooser` module in commit 91e4e1f.

app-proto/src/assembly.rs

@@ -13,7 +13,7 @@ use sycamore::prelude::*;
 use web_sys::{console, wasm_bindgen::JsValue}; /* DEBUG */
 
 use crate::{
-    display::DisplayItem,
+    components::{display::DisplayItem, outline::OutlineItem},
     engine::{
         Q,
         change_half_curvature,
@@ -29,7 +29,6 @@ use crate::{
         DescentHistory,
         Realization
     },
-    outline::OutlineItem,
     specified::SpecifiedValue
 };
 

app-proto/src/components.rs

@@ -0,0 +1,5 @@
+pub mod add_remove;
+pub mod diagnostics;
+pub mod display;
+pub mod outline;
+pub mod test_assembly_chooser;

app-proto/src/components/add_remove.rs

@@ -1,10 +1,10 @@
 use std::rc::Rc;
 use sycamore::prelude::*;
 
+use super::test_assembly_chooser::TestAssemblyChooser;
 use crate::{
     AppState,
-    assembly::{InversiveDistanceRegulator, Point, Sphere},
-    test_assembly_chooser::TestAssemblyChooser
+    assembly::{InversiveDistanceRegulator, Point, Sphere}
 };
 
 #[component]

app-proto/src/main.rs

@@ -1,11 +1,7 @@
-mod add_remove;
 mod assembly;
-mod diagnostics;
-mod display;
+mod components;
 mod engine;
-mod outline;
 mod specified;
-mod test_assembly_chooser;
 
 #[cfg(test)]
 mod tests;
@@ -13,11 +9,13 @@ mod tests;
 use std::{collections::BTreeSet, rc::Rc};
 use sycamore::prelude::*;
 
-use add_remove::AddRemove;
 use assembly::{Assembly, Element};
-use diagnostics::Diagnostics;
-use display::Display;
-use outline::Outline;
+use components::{
+    add_remove::AddRemove,
+    diagnostics::Diagnostics,
+    display::Display,
+    outline::Outline
+};
 
 #[derive(Clone)]
 struct AppState {