Re-link

Lints

More lints

Clippy

More

More clippy

Fmt

More doc work

More clippy

More

Author: Zeophlite

crates/bevy_ecs/src/system/builder.rs

@@ -106,7 +106,7 @@ use super::{Res, ResMut, SystemState};
 ///
 /// The implementor must ensure that the state returned
 /// from [`SystemParamBuilder::build`] is valid for `P`.
-/// Note that the exact safety requiremensts depend on the implementation of [`SystemParam`],
+/// Note that the exact safety requirements depend on the implementation of [`SystemParam`],
 /// so if `Self` is not a local type then you must call [`SystemParam::init_state`]
 /// or another [`SystemParamBuilder::build`].
 pub unsafe trait SystemParamBuilder<P: SystemParam>: Sized {

crates/bevy_text/Cargo.toml

@@ -10,6 +10,7 @@ keywords = ["bevy"]
 
 [features]
 default_font = []
+serde = []
 
 [dependencies]
 # bevy

crates/bevy_text/src/lib.rs

@@ -42,6 +42,7 @@ mod pipeline;
 mod text;
 mod text2d;
 mod text_access;
+pub mod undo_2;
 
 use bevy_camera::{visibility::VisibilitySystems, CameraUpdateSystems};
 pub use bounds::*;

crates/bevy_text/src/undo_2/README.md

@@ -1,6 +1,6 @@
-# Undo done the right way!
+# Undo done the right way
 
-Via https://gitlab.com/okannen/undo_2/-/tree/b32c34edb2c15c266b946f0d82188624f3aa3fdc
+Via [original](https://gitlab.com/okannen/undo_2/-/tree/b32c34edb2c15c266b946f0d82188624f3aa3fdc)
 
 ## Introduction
 
@@ -10,34 +10,33 @@ end of the Undo history as a precursor to your new change. I found the idea in
 [zaboople/klong][zaboople]. This crate is an implementation
 of this idea with a minor variation explained below.
 
-As an example consider the following sequence of commands: 
+As an example consider the following sequence of commands:
 
 | Command | State |
 | ------- | ----- |
-| Init    |       | 
+| Init    |       |
 | Do A    | A     |
 | Do B    | A, B  |
-| Undo    | A     | 
-| Do C    | A, C  | 
+| Undo    | A     |
+| Do C    | A, C  |
 
-With the **classical undo**, repeated undo would lead to the sequence: 
+With the **classical undo**, repeated undo would lead to the sequence:
 
 | Command | State |
 |---------|-------|
 |         | A, C  |
 | Undo    | A     |
-| Undo    |       | 
-
+| Undo    |       |
 
-Starting from 5, with **undo_2**, repeating undo would lead to the sequence: 
+Starting from 5, with **undo_2**, repeating undo would lead to the sequence:
 
 | Command | State |
 |---------|-------|
 |         | A, C  |
 | Undo    | A     |
-| Undo    | A,B   | 
-| Undo    | A     | 
-| Undo    |       | 
+| Undo    | A,B   |
+| Undo    | A     |
+| Undo    |       |
 
 **undo_2**'s undo navigates back in history, while classical undo navigates back
 through the sequence of command that builds the state.
@@ -53,11 +52,11 @@ and it is similar to vim :earlier.
   4. very lightweight, dumb and simple.
   5. possibility to merge and splice commands.
 
-## How to use it 
+## How to use it
 
 Add the dependency to the cargo file:
 
-```[toml]
+```toml
 [dependencies]
 undo_2 = "0.1"
 ```
@@ -74,7 +73,7 @@ be interpreted by the application. This design pattern makes implementation
 easier because it is not necessary to borrow data within the stored list of
 commands.
 
-```
+```rs
 use undo_2::{Commands,Action};
 use Action::{Do,Undo};
 
@@ -156,22 +155,22 @@ assert_eq!(editor.text, "a");
    forming the sequence are merged. This makes the traversal of the undo
    sequence more concise by avoiding state duplication.
 
-| Command | State   | Comment              | 
+| Command | State   | Comment              |
 |---------|-------  |----------------------|
-| Init    |         |                      | 
+| Init    |         |                      |
 | Do A    | A       |                      |
 | Do B    | A,B     |                      |
 | Do C    | A, B, C |                      |
-| Undo    | A, B    |Merged                | 
-| Undo    | A       |Merged                | 
-| Do D    | A, D    |                      | 
+| Undo    | A, B    |Merged                |
+| Undo    | A       |Merged                |
+| Do D    | A, D    |                      |
 | Undo    | A       |Redo the 2 Merged Undo|
-| Undo    | A, B, C |                      | 
-| Undo    | A, B    |                      | 
-| Undo    | A       |                      | 
-| Undo    |         |                      | 
+| Undo    | A, B, C |                      |
+| Undo    | A, B    |                      |
+| Undo    | A       |                      |
+| Undo    |         |                      |
 
-2. Each execution of an undos or redo may lead to the execution of a sequence of
+1. Each execution of an undos or redo may lead to the execution of a sequence of
    actions in the form `Undo(a)+Do(b)+Do(c)`. Basic arithmetic is implemented
    assuming that `Do(a)+Undo(a)` is equivalent to not doing anything (here the
    2 `a`'s designate the same entity, not to equal objects).
@@ -249,13 +248,14 @@ assert_eq!(editor.text, "az12");
 ```
 
 ## Release note
+
 ### Version 0.3
-  - [Action] is now an enum taking commands, the list of command to be
-  executed is of the form [Action<T>];
-  - added [Commands::can_undo] and [Commands::can_redo];
-  - added [Commands::rebuild], which correspond to the classical redo;
-  - fixed a bug in [Commands::undo_or_redo_to_index]
-  - Added support for special commands that represent a state setting. See [SetOrTransition].
 
-[zaboople]: https://github.com/zaboople/klonk/blob/master/TheGURQ.md
+- [`Action`] is now an enum taking commands, the list of command to be
+executed is of the form [`Action<T>`];
+- added [`Commands::can_undo`] and [`Commands::can_redo`];
+- added [`Commands::rebuild`], which correspond to the classical redo;
+- fixed a bug in [`Commands::undo_or_redo_to_index`]
+- Added support for special commands that represent a state setting. See [`SetOrTransition`].
 
+[zaboople]: https://github.com/zaboople/klonk/blob/master/TheGURQ.md