| 149 | | |
| 150 | | == Auto-detection of custom migration operations == |
| 151 | | |
| 152 | | || Difficulty || Hard. |
| 153 | | || Size || 350hrs |
| 154 | | || Potential Mentors || 2024 mentor: Mariusz Felisiak |
| 155 | | || Key Skills || Migrations Framework |
| 156 | | |
| 157 | | Allow auto-detection of custom migration operations. |
| 158 | | |
| 159 | | The auto-detector has its change-detection mostly hard-coded: [https://github.com/django/django/blob/main/django/db/migrations/autodetector.py#L104 autodetector.py#L104] |
| 160 | | |
| 161 | | It doesn't seem easy (or even possible with the current approach) to |
| 162 | | allow third-party code to intervene. The list of handlers to generated the individual operations would need to be data-driven, so that custom steps could be added. |
| 163 | | |
| 164 | | Expected outcome here would be a PR allowing auto-detection of custom migration operations. |
| 165 | | |
| 166 | | |