The serialization logic should be in different Serializer classes.
MigrationWriter.serialize() should call a Serializer Factory to obtain the
correct Serializer for the value passed in.
--
Ticket URL: <https://code.djangoproject.com/ticket/26151>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* has_patch: 0 => 1
* stage: Unreviewed => Accepted
Comment:
[https://github.com/django/django/pull/6059 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/26151#comment:1>
Comment (by MarkusH):
Looks good on the first glimpse :) . I'll need a bit more time to actually
look into it.
--
Ticket URL: <https://code.djangoproject.com/ticket/26151#comment:2>
* owner: nobody => yoongkang
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/26151#comment:3>
Comment (by MarkusH):
Since a discussion on #django-dev came up earlier I posted to the
developer mailing list to get other people's input:
https://groups.google.com/forum/#!topic/django-developers/yGKl7ZkLac4
--
Ticket URL: <https://code.djangoproject.com/ticket/26151#comment:4>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"4b1529e2cbee697e7e772b05ad5038edef22f38d" 4b1529e2]:
{{{
#!CommitTicketReference repository=""
revision="4b1529e2cbee697e7e772b05ad5038edef22f38d"
Fixed #26151 -- Refactored MigrationWriter.serialize()
Thanks Markus Holtermann for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26151#comment:5>