Split State
in separate views for Api
and CommHandle
- State changes can now be handled differently, depending on whether they were caused locallly (API) or by a remote peer (Comm) - State functions have more readable names (`write...` and `update...` have similar meanings, but using different names helps readability in the respective (API/Comm) context)
This commit is contained in:
parent
32bbe8a8ce
commit
98393b9bf6
16 changed files with 326 additions and 138 deletions
|
@ -1,9 +1,6 @@
|
|||
mod elements;
|
||||
pub mod elements;
|
||||
|
||||
pub use elements::*;
|
||||
|
||||
mod peers;
|
||||
pub use peers::*;
|
||||
pub mod peers;
|
||||
|
||||
|
||||
#[macro_export]
|
||||
|
@ -49,4 +46,4 @@ macro_rules! run_query {
|
|||
$db.run_script(query.as_str(), parameters, $mutability)
|
||||
}
|
||||
};
|
||||
}
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue