John Blackbourn
John Blackbourn
Thanks, the callback generation in general is quite buggy. I need to revisit it.
Do you think this is something specific to this extension or does it affect other autocomplete providers too?
Thinking out loud: I would quite like for the extension to auto-detect the existence of `${workspaceFolder}/hooks/(actions|filters).json` files, and prompt the user to use them for autocompletion if they exist. If...
The `$tax->cap->assign_terms` check is performed in about twenty places in core so if there was a bug here I would expect to have seen it by now. What's the error...
`--origin=user|role|all` could work.
I've tested this with WordPress 5.2.3 and with the latest trunk, and both exhibit the same result, but notably trunk marks the post as having missed its schedule.
It's worth noting that `WP_User::remove_cap( )` also suffers from the same problem. I'm not sure on WP-CLI's policy of improving upon core's APIs in this way.
`wp option list` always shows the raw value for options. It _could_ be extended to support the full list of formats (JSON, CSV, etc) but I'm not sure how useful...
It looks like this affects other fields too, such as `--user_nicename` and `--user_url`. See #301 .
The same thing applies to terms, users, and comments.