Rename ranges struct

Just an internal rename. I think it makes the intent clearer.
This will better fit the upcoming relationships support.

Author: Shatur

src/server/replication_messages.rs

@@ -1,4 +1,4 @@
-mod component_changes;
+mod change_ranges;
 pub(super) mod mutate_message;
 pub(super) mod serialized_data;
 pub(super) mod update_message;

…eplication_messages/component_changes.rs …er/replication_messages/change_ranges.rssrc/server/replication_messages/component_changes.rs renamed to src/server/replication_messages/change_ranges.rs src/server/replication_messages/component_changes.rs renamed to src/server/replication_messages/change_ranges.rs

@@ -9,13 +9,13 @@ use postcard::experimental::serialized_size;
 ///
 /// Used inside [`UpdateMessage`](super::update_message::UpdateMessage) and
 /// [`MutateMessage`](super::mutate_message::MutateMessage).
-pub(super) struct ComponentChanges {
+pub(super) struct ChangeRanges {
     pub(super) entity: Range<usize>,
     pub(super) components_len: usize,
     pub(super) components: Vec<Range<usize>>,
 }
 
-impl ComponentChanges {
+impl ChangeRanges {
     /// Returns serialized size.
     pub(super) fn size(&self) -> Result<usize> {
         let len_size = serialized_size(&self.components_len)?;

src/server/replication_messages/mutate_message.rs

@@ -3,7 +3,7 @@ use core::{ops::Range, time::Duration};
 use bevy::{ecs::component::Tick, prelude::*};
 use postcard::experimental::{max_size::MaxSize, serialized_size};
 
-use super::{component_changes::ComponentChanges, serialized_data::SerializedData};
+use super::{change_ranges::ChangeRanges, serialized_data::SerializedData};
 use crate::shared::{
     backend::{replicon_channels::ReplicationChannel, replicon_server::RepliconServer},
     postcard_utils,
@@ -50,7 +50,7 @@ pub(crate) struct MutateMessage {
     /// of chunk bytes instead of the number of components. This is because, during deserialization,
     /// some entities may be skipped if they have already been updated (as mutations are sent until
     /// the client acknowledges them).
-    mutations: Vec<ComponentChanges>,
+    mutations: Vec<ChangeRanges>,
 
     /// Indicates that an entity has been written since the
     /// last call of [`Self::start_entity_mutations`].
@@ -83,7 +83,7 @@ impl MutateMessage {
     /// Adds an entity chunk.
     pub(crate) fn add_mutated_entity(&mut self, entity: Entity, entity_range: Range<usize>) {
         let components = self.buffer.pop().unwrap_or_default();
-        self.mutations.push(ComponentChanges {
+        self.mutations.push(ChangeRanges {
             entity: entity_range,
             components_len: 0,
             components,
@@ -103,7 +103,7 @@ impl MutateMessage {
     }
 
     /// Returns written mutations for the last entity from [`Self::add_mutated_entity`].
-    pub(super) fn last_mutations(&mut self) -> Option<&ComponentChanges> {
+    pub(super) fn last_mutations(&mut self) -> Option<&ChangeRanges> {
         self.mutations.last()
     }
 

src/server/replication_messages/update_message.rs

@@ -4,8 +4,7 @@ use bevy::prelude::*;
 use postcard::experimental::serialized_size;
 
 use super::{
-    component_changes::ComponentChanges, mutate_message::MutateMessage,
-    serialized_data::SerializedData,
+    change_ranges::ChangeRanges, mutate_message::MutateMessage, serialized_data::SerializedData,
 };
 use crate::server::client_visibility::Visibility;
 use crate::shared::{
@@ -66,7 +65,7 @@ pub(crate) struct UpdateMessage {
     /// Serialized as a list of pairs of entity chunk and a list of
     /// [`FnsId`](crate::shared::replication::replication_registry::FnsId)
     /// serialized as a single chunk.
-    removals: Vec<ComponentRemovals>,
+    removals: Vec<RemovalRanges>,
 
     /// Component insertions or mutations that happened in this tick.
     ///
@@ -76,7 +75,7 @@ pub(crate) struct UpdateMessage {
     ///
     /// Usually mutations are stored in [`MutateMessage`], but if an entity has any insertions or removal,
     /// or the entity just became visible for a client, we serialize it as part of the update message to keep entity updates atomic.
-    changes: Vec<ComponentChanges>,
+    changes: Vec<ChangeRanges>,
 
     /// Visibility of the entity for which component changes are being written.
     ///
@@ -115,7 +114,7 @@ impl UpdateMessage {
         ids_len: usize,
         fn_ids: Range<usize>,
     ) {
-        self.removals.push(ComponentRemovals {
+        self.removals.push(RemovalRanges {
             entity,
             ids_len,
             fn_ids,
@@ -145,7 +144,7 @@ impl UpdateMessage {
     /// Adds an entity chunk.
     pub(crate) fn add_changed_entity(&mut self, entity: Range<usize>) {
         let components = self.buffer.pop().unwrap_or_default();
-        self.changes.push(ComponentChanges {
+        self.changes.push(ChangeRanges {
             entity,
             components_len: 0,
             components,
@@ -175,7 +174,7 @@ impl UpdateMessage {
 
         if !self.entity_written {
             let components = self.buffer.pop().unwrap_or_default();
-            let changes = ComponentChanges {
+            let changes = ChangeRanges {
                 entity: mutations.entity.clone(),
                 components_len: 0,
                 components,
@@ -229,15 +228,15 @@ impl UpdateMessage {
                     message_size += self
                         .removals
                         .iter()
-                        .map(ComponentRemovals::size)
+                        .map(RemovalRanges::size)
                         .sum::<Result<usize>>()?;
                 }
                 UpdateMessageFlags::CHANGES => {
                     debug_assert_eq!(flag, last_flag);
                     message_size += self
                         .changes
                         .iter()
-                        .map(ComponentChanges::size)
+                        .map(ChangeRanges::size)
                         .sum::<Result<usize>>()?;
                 }
                 _ => unreachable!("iteration should yield only named flags"),
@@ -330,13 +329,13 @@ impl UpdateMessage {
     }
 }
 
-struct ComponentRemovals {
+struct RemovalRanges {
     entity: Range<usize>,
     ids_len: usize,
     fn_ids: Range<usize>,
 }
 
-impl ComponentRemovals {
+impl RemovalRanges {
     fn size(&self) -> Result<usize> {
         let len_size = serialized_size(&self.ids_len)?;
         Ok(self.entity.len() + len_size + self.fn_ids.len())