You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The descriptions for the second-level subcommands of wp post|user term|meta use generic "object" terminology from the method docblocks in the abstract CommandWithTerms and CommandWithMeta classes. For example:
wp post term --help correctly says "Adds, updates, removes, and lists post terms."
wp post term list --help uses the generic phrase "List all terms associated with an object."
Generic terminology is used for all four term and meta subcommands:
This is because most of the code is in a shared abstract class, so the docblocks only exist once for all "objects".
I agree that it would be preferable to get rid of the generic terms, though. I'll have a look to see how best to achieve that without copying the logic around.
The descriptions for the second-level subcommands of
wp post|user term|meta
use generic "object" terminology from the method docblocks in the abstractCommandWithTerms
andCommandWithMeta
classes. For example:wp post term --help
correctly says "Adds, updates, removes, and lists post terms."wp post term list --help
uses the generic phrase "List all terms associated with an object."Generic terminology is used for all four term and meta subcommands:
wp (post|user) (term|meta) (add|list|remove|set) --help
It would be great if the descriptions and argument synopses for these commands didn't use generic terminology.
The text was updated successfully, but these errors were encountered: