refactor: use consistent format for expects

Author: DanielleHuisman

examples/basic/src/user.rs

@@ -4,7 +4,7 @@ use fortifier::Validate;
 use regex::Regex;
 
 static COUNTRY_CODE_REGEX: LazyLock<Regex> =
-    LazyLock::new(|| Regex::new(r"[A-Z]{2}").expect("Regex should be valid."));
+    LazyLock::new(|| Regex::new(r"[A-Z]{2}").expect("valid regex"));
 
 #[derive(Validate)]
 pub struct CreateUser {

packages/fortifier-macros/src/validate/type.rs

@@ -106,7 +106,7 @@ mod tests {
     use super::should_validate_type;
 
     fn validate(tokens: TokenStream) -> bool {
-        should_validate_type(&syn::parse2(tokens).expect("Type should be valid."))
+        should_validate_type(&syn::parse2(tokens).expect("valid type"))
     }
 
     #[test]

packages/fortifier/src/validations/regex.rs

@@ -150,8 +150,7 @@ mod tests {
 
     use super::{RegexError, ValidateRegex};
 
-    static REGEX: LazyLock<Regex> =
-        LazyLock::new(|| Regex::new(r"[0-9]{4}").expect("Regex should be valid."));
+    static REGEX: LazyLock<Regex> = LazyLock::new(|| Regex::new(r"[0-9]{4}").expect("valid regex"));
 
     #[test]
     fn ok() {

packages/fortifier/src/validations/url.rs

@@ -250,7 +250,7 @@ mod tests {
         );
         assert_eq!(
             Url::parse("http://localhost")
-                .expect("URL should be valid.")
+                .expect("valid URL")
                 .validate_url(),
             Ok(())
         );

packages/fortifier/tests/serde.rs

@@ -82,7 +82,7 @@ fn serialize() {
     let (deserialized, serialized) = setup();
 
     assert_eq!(
-        serde_json::to_value(&deserialized).expect("Value should be serializable."),
+        serde_json::to_value(&deserialized).expect("serializable value"),
         serialized
     );
 }
@@ -93,7 +93,7 @@ fn deserialize() {
 
     assert_eq!(
         serde_json::from_value::<ValidationErrors<TestError>>(serialized)
-            .expect("Value should be deserializable."),
+            .expect("deserializable value"),
         deserialized,
     );
 }