Move ide::AnalysisChange -> base_db::Change

This seems like a better factoring logically; ideally, clients shouldn't touch
`set_` methods of the database directly. Additionally, I think this
should remove the unfortunate duplication in fixture code.

1 files changed, 2 insertions, 2 deletions

diff --git a/crates/ide/src/parent_module.rs b/crates/ide/src/parent_module.rs
index 59ed2967c..68b107901 100644
--- a/crates/ide/src/parent_module.rs
+++ b/crates/ide/src/parent_module.rs
@@ -69,7 +69,7 @@ mod tests {
 
     use crate::{
         mock_analysis::{analysis_and_position, MockAnalysis},
-        AnalysisChange, CrateGraph,
+        Change, CrateGraph,
         Edition::Edition2018,
     };
 
@@ -146,7 +146,7 @@ mod foo;
             Env::default(),
             Default::default(),
         );
-        let mut change = AnalysisChange::new();
+        let mut change = Change::new();
         change.set_crate_graph(crate_graph);
         host.apply_change(change);