I've worked up a solution for
feedback. https://github.com/tim-schilling/django/pull/1
On Sunday, February 3, 2019 at 11:30:34 AM UTC-6, Tim Schilling wrote:
>
> My idea is to add the applied datetime value to the showmigrations command.
>
> I've run into the case where I'm working on a branch
I personally like the option better. This seems like a different use-case
than I'd normally expect from a verbosity level.
On Sun, Feb 3, 2019 at 12:45 PM Tim Schilling
wrote:
> Not changing the default output makes a lot of sense. I initially was
> wondering if it should have its own option.
Not changing the default output makes a lot of sense. I initially was
wondering if it should have its own option. Making it an addition to a
higher verbosity level will work too.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to
Hello,
This sounds interesting.
You should think a bit about backwards compatibility because there's a good
chance that some users are calling django-admin showmigrations in scripts or
tools. I don't think this is a blocker for changing the output format. However
you should plan to minimize
My idea is to add the applied datetime value to the showmigrations command.
I've run into the case where I'm working on a branch that involves a number
of migrations across various apps, but then have to switch to a different
branch which has different migrations. It can be troublesome to
