Fix new typos (#19562)
# Objective Fix new typos found on new version of `typos` (#19551) ## Solution Fix typos
This commit is contained in:
parent
0381a798e2
commit
f5f092f2f3
@ -2053,7 +2053,7 @@ impl Components {
|
|||||||
}
|
}
|
||||||
|
|
||||||
/// Gets the metadata associated with the given component, if it is registered.
|
/// Gets the metadata associated with the given component, if it is registered.
|
||||||
/// This will return `None` if the id is not regiserted or is queued.
|
/// This will return `None` if the id is not registered or is queued.
|
||||||
///
|
///
|
||||||
/// This will return an incorrect result if `id` did not come from the same world as `self`. It may return `None` or a garbage value.
|
/// This will return an incorrect result if `id` did not come from the same world as `self`. It may return `None` or a garbage value.
|
||||||
#[inline]
|
#[inline]
|
||||||
|
@ -49,7 +49,7 @@ This means that where `Result<T, IdentifierError>` was returned, `Option<T>` is
|
|||||||
It is well documented that both the bit format, serialization, and `Ord` implementations for `Entity` are subject to change between versions.
|
It is well documented that both the bit format, serialization, and `Ord` implementations for `Entity` are subject to change between versions.
|
||||||
Those have all changed in this version.
|
Those have all changed in this version.
|
||||||
|
|
||||||
For entity ordering, the order still prioretizes an entity's generation, but after that, it now considers higher index entities less than lower index entities.
|
For entity ordering, the order still prioritizes an entity's generation, but after that, it now considers higher index entities less than lower index entities.
|
||||||
|
|
||||||
The changes to serialization and the bit format are directly related.
|
The changes to serialization and the bit format are directly related.
|
||||||
Effectively, this means that all serialized and transmuted entities will not work as expected and may crash.
|
Effectively, this means that all serialized and transmuted entities will not work as expected and may crash.
|
||||||
|
@ -14,6 +14,6 @@ They were deprecated in 0.16 for being unnecessary with the retained render worl
|
|||||||
|
|
||||||
Instead of these functions consider doing one of the following:
|
Instead of these functions consider doing one of the following:
|
||||||
|
|
||||||
Option A) Instead of despawing entities, insert the `Disabled` component, and instead of respawning them at particular ids, use `try_insert_batch` or `insert_batch` and remove `Disabled`.
|
Option A) Instead of despawning entities, insert the `Disabled` component, and instead of respawning them at particular ids, use `try_insert_batch` or `insert_batch` and remove `Disabled`.
|
||||||
|
|
||||||
Option B) Instead of giving special meaning to an entity id, simply use `spawn_batch` and ensure entity references are valid when despawning.
|
Option B) Instead of giving special meaning to an entity id, simply use `spawn_batch` and ensure entity references are valid when despawning.
|
||||||
|
Loading…
Reference in New Issue
Block a user