Fix when coerce_numbers_to_str enabled and string has invalid unicode character (#1515)

Co-authored-by: Andrei Berenda <aberenda@optifino.com>

Author: andrey-berenda

src/validators/string.rs

@@ -200,15 +200,14 @@ impl StrConstrainedValidator {
     }
 
     // whether any of the constraints/customisations are actually enabled
-    // except strict which can be set on StrValidator
+    // except strict and coerce_numbers_to_str which can be set on StrValidator
     fn has_constraints_set(&self) -> bool {
         self.pattern.is_some()
             || self.max_length.is_some()
             || self.min_length.is_some()
             || self.strip_whitespace
             || self.to_lower
             || self.to_upper
-            || self.coerce_numbers_to_str
     }
 }
 

tests/validators/test_string.py

@@ -286,6 +286,14 @@ class StrSubclass(str):
     assert not isinstance(v.validate_python(StrSubclass(''), strict=True), StrSubclass)
 
 
+@pytest.mark.parametrize('string', [True, False])
+def test_coerce_numbers_to_str_with_invalid_unicode_character(string) -> None:
+    config = core_schema.CoreConfig(coerce_numbers_to_str=True)
+
+    v = SchemaValidator(core_schema.str_schema(strict=string), config)
+    assert v.validate_python('\ud835') == '\ud835'
+
+
 def test_coerce_numbers_to_str_disabled_in_strict_mode() -> None:
     config = core_schema.CoreConfig(coerce_numbers_to_str=True)