refactor: Reorder test enums

Author: NickLarsenNZ

kube-core/src/schema/transform_properties.rs

@@ -1,4 +1,4 @@
-use crate::schema::{InstanceType, Metadata, Schema, SchemaObject, SingleOrVec, NULL_SCHEMA};
+use crate::schema::{InstanceType, Schema, SchemaObject, SingleOrVec, NULL_SCHEMA};
 
 /// Take oneOf or anyOf subschema properties and move them them into the schema
 /// properties.

kube-derive/tests/crd_mixed_enum_test.rs

@@ -57,13 +57,13 @@ enum InvalidEnum5Spec {
 #[kube(group = "clux.dev", version = "v1", kind = "ValidEnum6")]
 #[serde(untagged)]
 enum ValidEnum6Spec {
-    B {
+    A {
         /// The inner fields need to have the same schema (so also same description)
         inner: u32,
         /// An additional field
         additional: String,
     },
-    A {
+    B {
         /// The inner fields need to have the same schema (so also same description)
         inner: u32,
     },
@@ -75,12 +75,12 @@ enum ValidEnum6Spec {
 #[kube(group = "clux.dev", version = "v1", kind = "InvalidEnum7")]
 #[serde(untagged)]
 enum InvalidEnum7Spec {
-    B {
+    A {
         /// The inner fields need to have the same schema (so also same description)
         inner: u32,
         additional: String,
     },
-    A {
+    B {
         /// This description differs!
         inner: u32,
     },
@@ -269,6 +269,7 @@ fn valid_enum_4() {
 fn invalid_enum_5() {
     InvalidEnum5::crd();
 }
+
 #[test]
 fn valid_enum_6() {
     assert_json_eq!(