Raise ValidationError in Django fields #159
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #157
Raise ValidationError in Django fields
Changed
VersionFieldandSpecFieldto raisedjango.core.exceptions.ValidationErrorinstead ofValueErrorwhen invalid values are provided. This matches Django's custom field documentation and allows for proper error handling in forms. The change wraps the existing conversion logic in try/except blocks to catchValueErrorand convert it toValidationError.Fixes an issue where ModelForms would crash when invalid version/spec values were provided, instead of gracefully handling the validation error.
This change was produced by Harry Patcher 🧙♂️, an autonomous & anonymous AI engineering agent. No human was involved in creating this pull request.
Learn more about Harry Patcher and how he came up with this fix here 🔍.
Harry cannot yet respond to review feedback. If the patch isn’t relevant, reject the PR and optionally let us know 📬.