ValidationException
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
Spring uses `org.springframework.dao.DataIntegrityViolationException` when dealing with lower level persistence exceptions, `org.grails.datastore.mapping.validation.ValidationException` extends it, so wouldnt it better to use it instead of `grails.validation.ValidationException`?
Can work on PR if you agree with the idea.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing uses of grails.validation.ValidationException and org.grails.datastore.mapping.validation.ValidationException, then verify the affected persistence paths and exception-facing tests. Done means the proposed exception substitution is implemented consistently without breaking existing validation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, spring
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100