sort derives with cargo sort-derives

might add to ci later, unsure how to do it without adding significant friction for contributors though

1 files changed, 4 insertions, 4 deletions

diff --git a/azalea-protocol/src/packets/game/c_update_recipes.rs b/azalea-protocol/src/packets/game/c_update_recipes.rs
index de9f6e3b..eee89d28 100644
--- a/azalea-protocol/src/packets/game/c_update_recipes.rs
+++ b/azalea-protocol/src/packets/game/c_update_recipes.rs
@@ -7,23 +7,23 @@ use azalea_registry::builtin::ItemKind;
 
 use crate::common::recipe::{Ingredient, SlotDisplayData};
 
-#[derive(Clone, Debug, AzBuf, PartialEq, ClientboundGamePacket)]
+#[derive(AzBuf, ClientboundGamePacket, Clone, Debug, PartialEq)]
 pub struct ClientboundUpdateRecipes {
     pub item_sets: HashMap<Identifier, RecipePropertySet>,
     pub stonecutter_recipes: Vec<SingleInputEntry>,
 }
 
-#[derive(Clone, Debug, PartialEq, AzBuf)]
+#[derive(AzBuf, Clone, Debug, PartialEq)]
 pub struct SingleInputEntry {
     pub input: Ingredient,
     pub recipe: SelectableRecipe,
 }
-#[derive(Clone, Debug, PartialEq, AzBuf)]
+#[derive(AzBuf, Clone, Debug, PartialEq)]
 pub struct SelectableRecipe {
     pub option_display: SlotDisplayData,
 }
 
-#[derive(Clone, Debug, PartialEq, AzBuf)]
+#[derive(AzBuf, Clone, Debug, PartialEq)]
 pub struct RecipePropertySet {
     pub items: Vec<ItemKind>,
 }