#35251: dumpdata refactoring
-------------------------------------+-------------------------------------
Reporter: Hovi | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: 5.0
commands) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Hovi):
I don't need to modify serializers. That's the part I want to reuse as it
is. I don't expect management commands to be universal tools, but that
doesn't mean they cannot be more flexible so that when I wanna customize
them (because they are not universal enough for me), I can do that without
just copy-pasting the whole file.
What I intend to do mostly is to create my own custom way to filter
apps/models/model instances while pretty much keeping the rest the same.
One way how can I reuse it is to use `call_command`, passing loads and
loads PKs but that is less flexible and definitely feels wrong for various
reasons.
--
Ticket URL: <https://code.djangoproject.com/ticket/35251#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018de664f5bd-2e6866b5-e895-4b71-8c28-2d4c7a3f6037-000000%40eu-central-1.amazonses.com.
