[Django] #33320: Inconsistencies around --no-input flags
Django
-----------------------------------------+------------------------
Reporter: Peter Law | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 1 |
-----------------------------------------+------------------------
I realise this is a really small thing, but I get gotcha'd by it quite a
lot.
Some Django commands take a `--no-input` flag while others take a
`--noinput` flag. This means that rather than being able to just type a
spelling you've learned, you need to look it up for each command (or try
it and have it fail).
Given that `--no-colour` has the interstitial dash, I suggest
consolidating around that spelling (i.e: `--no-input`) for consistency,
but I don't feel strongly as long as there's only one spelling of the no-
input flag.
It even seems reasonable for a while for Django commands which currently
accept the "other" spelling to accept both (perhaps with a warning), so
there's a good upgrade path here for people or scripts which are used to
the current arrangement.
--
Ticket URL: <https://code.djangoproject.com/ticket/33320>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: Peter Law | Owner: nobody
Component: Core (Management | Version: 3.2
commands) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
* ui_ux: 1 => 0
* component: Uncategorized => Core (Management commands)
* easy: 1 => 0
Comment:
> Some Django commands take a `--no-input` flag while others take a
`--noinput` flag. This means that rather than being able to just type a
spelling you've learned, you need to look it up for each command (or try
it and have it fail).
All built-in commands accept both `--noinput` and `--no-input` since
Django 1.9.
--
Ticket URL: <https://code.djangoproject.com/ticket/33320#comment:1>
Django
Reporter: Peter Law | Owner: nobody
Component: Core (Management | Version: 3.2
commands) |
Severity: Normal | Resolution: invalid
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------------+-------------------------------------
Comment (by Peter Law):
Oh, sorry. `drop_test_database` was the one I'm hitting this on. I'd
assumed that that was a built-in, though it turns out not to be (it's in
`django-extensions`). Sorry about that.
--
Ticket URL: <https://code.djangoproject.com/ticket/33320#comment:2>