| | 1 | Hi, I’m interested in working on this. |
| | 2 | From what I understand, the goal is to extract the existing TypeSerializer logic for determining a module path into a reusable helper in django.utils, and ensure it covers edge cases where f"{val.__module__}.{val.__qualname__}" isn’t sufficient. |
| | 3 | My plan would be: |
| | 4 | |
| | 5 | Review and adapt the current implementation in django.migrations.serializer.TypeSerializer. |
| | 6 | |
| | 7 | Add unit tests for different input types (functions, classes, nested classes, builtins, etc.). |
| | 8 | |
| | 9 | Place the helper in django.utils and update the current usages in the codebase to use it. |
| | 10 | |
| | 11 | Could you confirm if this approach makes sense, and if there’s a preferred name/location for the helper before I start a patch? |