[proofing] search+replace function

[kvchitrapu]

Feature

Search and replace a string works. May need stylesheet changes to pretty it up. Completes #455.

Tests

[akprasad]

Thanks for this. Here's the flow I have in mind:

1. Default page -- user sees a search/replace box, fills it in, and submits.
2. Preview page -- user sees all of the changes that will be made in the given text and is given an option to confirm
3. Confirmation page -- when user confirms, we create a new revision for each affected page. On the frontend, we return to (1) and show a message like "Made X replacements across Y pages."

IIUC this PR completes the implementation of (2). Do you feel comfortable trying (3) as well?

[kvchitrapu]

Thanks for this. Here's the flow I have in mind:

1. Default page -- user sees a search/replace box, fills it in, and submits.
2. Preview page -- user sees all of the changes that will be made in the given text and is given an option to confirm
3. Confirmation page -- when user confirms, we create a new revision for each affected page. On the frontend, we return to (1) and show a message like "Made X replacements across Y pages."

IIUC this PR completes the implementation of (2). Do you feel comfortable trying (3) as well?

You're right. I completed #2.

From our previous exchange on this issue, I understood that the user manually cherrypicks the changes and updates the edit page.

What you listed as #3 is key to a better proofer experience. I'll give it a shot.

[akprasad]

Thanks -- please feel free to give #3 a shot as part of this PR.

[kvchitrapu]

Thanks -- please feel free to give #3 a shot as part of this PR.

I made the required changes. Now testing and debugging them. I am hoping to send a PR update this weekend.

[kvchitrapu]

Thanks -- please feel free to give #3 a shot as part of this PR.

I made the required changes. Now testing and debugging them. I am hoping to send a PR update this weekend.

@akprasad, I found a code bug on Saturday but haven't had a chance to work on it yet. I'll resolve the issue as soon as possible.

[kvchitrapu]

@akprasad , I have the end-to-end flow working. Please review. Unittest coverage is not at 80%. I'll check tomorrow.

Potential Improvements
While the overall functionality works, the code quality could be better. I am not familiar with JavaScript and UI code.

1. UI, colors, checkboxes, and wording can be improved.
2. The "Check-all/Uncheck-all" boxes need refinement, particularly in JavaScript.
3. The way changes are carried back and forth between HTML code and server code in form fields can be improved, as there is no pagination available at this time.
4. There may be better ways to name the form fields for match{{page-slug}}-{{line-number}}-replace to mark each selected phrase for replacement. I chose the simplest implementation.
5. No translations have been done.