Closed (duplicate)
Project:
Drush
Version:
8.x-6.x-dev
Component:
Documentation
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
13 May 2013 at 16:10 UTC
Updated:
24 Aug 2013 at 06:49 UTC
Mostly with documentation/reality discrepancies, but here are some things I found while testing out drush 8.x-6x:
Also, I noticed that print-r, json, export, and config are valid options, but are hardly ever mentioned. Should they be added to the default list of formats?
I'll be happy to make a docs patch if these things can be cleared up solely with documentation, the other things require more knowledge than I have.
Comments
Comment #1
greg.1.anderson commentedMany of the problems here will go away once we simplify the available output formats in #1959466: Reduce number of formats and/or do better guessing about what format user meant to use.. Let's wait until that issue lands, then re-analyze everything above, and tackle the remaining problems then.
Regarding print-r, json, export, and config, yes, these pretty much always work, but they are rarely mentioned in the help output because it would be too repetitious. Note that these are all listed when you run help in --verbose mode.
Comment #1.0
moshe weitzman commentedNumbered the items
Comment #1.1
moshe weitzman commentedUpdated issue summary.
Comment #1.2
moshe weitzman commentedUpdated issue summary.
Comment #2
moshe weitzman commentedThanks for compiling this list. I numbered the items in the Summary, so we can discuss them better. I crossed out a few that I think are OK. Please keep on nitpicking these docs - I really appreciate it. Some items have been fixed since this issue was filed.
1. core-requirements: Summary is the same as 'value'. I don't know why this is, but thats evident in the field-labels definition for this command. FYI, you can see exactly what the command callback returned by using
--format=var_export.2. core-status: We do show '--fields' now. Yes, key-value commands sufficiently unlike "table" commands and that they don't allow csv. The formats that are allowed are listed. I think this is OK.
3. help: When I pass --filter with no value, I get a prompt to pick a value which is pretty handy, IMO. help command does not yet support --format which is a bit sad. We'd have to change the output a bit to get it to do so.
4. php-eval: I agree this is a bit surprising, but I think it is OK. Drush will format your return value according to --format, if there is any.
5. config-get: yaml (and json, var_export) are now always shown. But it does happen that the default value is not in the available values list. The bug appears to be in drush_merge_engine_data() but I can't track it down. Help appreciated.
6. field-info: ini formatter is gone. other formats working fine.
7. pm-info: I think the layout is OK. It is a bunch of key-value groups, one after another. Are you expecting something different?
8. pm-list: I'm seeing this too. Seems like a bug. Any idea Greg? Should key-value format not be listed? This happens several times later in the list.
9. pm-updatestatus: ini is gone.
10. role-list: --filter working for me.
11: user-information: csv working as expected. list is supposed to only show one column. i think we are ok.
12: cache-get: yeah, we list too many formats here. Greg?
13+ The rest are OK - covered in items above
Comment #3
moshe weitzman commentedhttps://github.com/drush-ops/drush/issues/8
Comment #3.0
moshe weitzman commentedUpdated issue summary.
Comment #4
greg.1.anderson commented1. Fixed this in https://github.com/drush-ops/drush/issues/8
8. pm-list no longer lists key-value as an option; must have been fixed in a previous commit.
Comment #4.0
greg.1.anderson commentedMark core-requirements / summary field task as done.
Comment #5
greg.1.anderson commentedFixed 5 and 12 by reducing the number of formats shown in help for these commands. Also, if the default format normally wouldn't be shown in the help's list of available formats (e.g. because it is only shown in verbose mode), insure that it is shown anyway.
Comment #5.0
greg.1.anderson commentedpm-list key-value is working now; strike it off the list.
Comment #5.1
greg.1.anderson commentedMarked 5 and 12 done.