My name is Manav. I’m a Computer Science and Engineering junior at Dr. A.P.J. Abdul Kalam Technical University in India.
I have solved many issues on trac
I read through the GSoC Idea List and the Migration topic stood out for me. I found the idea to adapt schema editors to operate from model states instead of fake rendered models really interesting.
I am going through the code for the Migrations framework for the last 2 weeks. I started from django.core.management.commands.makemigrations and django.core.management.commands.migrate, Then I read the source code of all the functions and classes that are used in both the modules. In the meantime I was reading the closed migration tickets and also solved one of the migrations problem of naming the migrations file.
When I researched more about the problem, I came to know that a fake model is rendered by the render() function. I am still trying to figure out how can we use Model State on practical level. I even read the comment by @MarkusH which gave me the idea of digging into the field level and also learned that as the API is documented all the things have to keep working as-is.
In the comment, Markus suggested a good idea, and currently, I am figuring this out.
Also, I would like to thank @MarkusH for his initial patch (Commits · MarkusH/django · GitHub) which helped me a lot while thinking of an optimized solution and I feel that such efforts shouldn’t be wasted.
To be honest, I am contributing to the Django project for the last 6 to 7 months and I found the community friendly and helpful. I would appreciate any suggestions, thoughts on how can I propose the best solution.