Show actual transformations taking place about search-replace-command HOT 8 CLOSED

Huh. That's not awful then, I suppose.

from search-replace-command.

I'd like to give this a bash. I'm thinking of doing it by adding a new option [--log[=<file>]]?

Also I think a new command search should be added here for convenience which just defaults the <new> arg to null and sets the --dry-run option to true and the new log option to true (unless already set). This in addition to merging the db ack command wp-cli/db-command#7 (which I'll also do) as although there's significant overlap it seems very natural to have a search command (in effect an alias) that behaves like this (plus it's easy to do!).

from search-replace-command.

Also I think a new command search should be added here for convenience which just defaults the <new> arg to null and sets the --dry-run option to true and the new log option to true (unless already set).

My preference would be to focus on wp db ack for now, until it can be established the search command fills a distinct need. Difference use cases around the same feature are better solved with documentation.

from search-replace-command.

Okay, will leave it out. Do you think [--log[=<file>]] is the right approach? Would also add supporting options like [[--log-context=<num_words>]] or similar.

from search-replace-command.

Do you think [--log[=<file>]] is the right approach?

Not particularly. I'd display to STDOUT, which gives the user more control over where the data ends up.

from search-replace-command.

I mean for it to behave like [--export=[<file>]], so a simple --log would go to STDOUT.

from search-replace-command.

Now that we have wp db search, can we close this issue?

I'm not sure it's realistic to produce a visual report of the transformations taking place; this seems more effort than it's worth.

Instead, it'd be good to know what use case isn't already solved by wp db search.

from search-replace-command.

Here's a prototype output:

from search-replace-command.