@DirtyCheck for abstract classes inherited by domains mentioned only in upgrade notes
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
The section that explains the changes in default dirty checking and @DirtyCheck usage for abstract classes inherited by domain classes for GORM 6.1.x is given only in [upgrade notes](http://gorm.grails.org/6.1.x/hibernate/manual/#upgradeNotes) but there are no corresponding changes in the [5.3. Inheritance in GORM](http://gorm.grails.org/6.1.x/hibernate/manual/#inheritanceInGORM) section.
This small inconsistency caused some struggle and research.
Thanks in advance.
Contributor guide
Research direction
Compare the GORM 6.1.x upgrade notes with the 5.3 Inheritance in GORM section linked in the issue, focusing on @DirtyCheck for abstract classes inherited by domain classes. Update the inheritance documentation so it covers the same behavior and usage described in the upgrade notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100