tests/main/test_main_general.py (1)

477-552: New SchemaParseError tests cover key behaviors

The four tests collectively verify:

• Integration with generate() for both flat and nested schemas (including $defs/MyModel path),
• Preservation of original_error and path,
• Message formatting when path is omitted.

They are focused, resilient (regex-based), and exercise the intended API surface well.

If you want slightly stronger guarantees, you could also assert on exc_info.value.path contents in the nested-path test (e.g., that it ends with ["#/$defs", "MyModel"]), but the current coverage is already solid.

src/datamodel_code_generator/__init__.py (1)

393-414: SchemaParseError design and export look correct

• The class cleanly extends Error, preserves the original exception via original_error, and adds structured path information while formatting a human-readable message.
• Defaulting path to [] and formatting only when non-empty matches the tests’ expectations (both with and without path).
• Adding "SchemaParseError" to __all__ makes the type publicly consumable, which is consistent with how it’s used in tests and in the JSON Schema parser.

If you later need to distinguish the raw message from the path-augmented one, consider storing the unformatted message in a separate attribute (e.g., base_message), but it’s not necessary for the current use cases.

Also applies to: 1005-1025

src/datamodel_code_generator/parser/jsonschema.py (1)

24-40: Centralized schema-object validation with SchemaParseError is well-structured

• Importing SchemaParseError here and introducing _validate_schema_object() gives a single, consistent place to wrap low-level validation failures into a richer error that includes path and original_error.
• The except SchemaParseError: raise clause avoids double-wrapping if future callers already raise that type, while the broad except Exception as e correctly captures any validation/runtime issues from model_validate.
• Using message=f"{type(e).__name__}: {e}" preserves the original exception type in the human-facing message, while the underlying exception remains available via original_error for advanced consumers.

You might later consider also routing other internal model_validate(self.SCHEMA_OBJECT_TYPE, ...) call sites (e.g., in _load_ref_schema_object or merge helpers) through _validate_schema_object so that all schema-object construction failures benefit from path-aware SchemaParseError, but the current scope is already an improvement aligned with the PR goal.

Also applies to: 3109-3134

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro