Pro 4504 inline figure

[haroun]

Summary

Fix inline figure in rich-text + Remove empty paragraph from rich text widget tasks

What are the specific steps to test this change?

1. Run the task node app.js @apostrophecms/rich-text-widget:fix-inline-figure and confirm
2. Run the task node app.js @apostrophecms/rich-text-widget:remove-empty-paragraph and confirm
3. Integration tests must be green

What kind of change does this PR introduce?

(Check at least one)

• Bug fix
• New feature
• Refactor
• Documentation
• Build-related changes
• Other

Make sure the PR fulfills these requirements:

• It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
• The changelog is updated
• Related documentation has been updated
• Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

[linear]

PRO-4504 There is an issue with padding and/or Image and text justification since upgrading to A3.

Utah was upgraded to Apostrophe 3 (by us) and they've been finding some styles that are broken. The two examples he provides are here:

• There is now a large empty space between some text and images that are supposed to be in-line with each other. Example: Is This Normal? What to Do with the Stress in Your Body
• There is also text overlapping with images, some images are not displaying, some images have been enlarged, and some of the in-line text with the images is not the right font (should be Roboto). Example: When Emotions Run High, Here’s How to Respond

Note: Do not start without a code walkthrough if you are new to this project.

[boutell]

A confirmation prompt is surprising behavior from a command line system task, especially in a production environment, so I would suggest requiring the user to run it again with a --confirm option.

[boutell]

Stray log

[haroun]

I've added a --force to skip the prompt.

[boutell]

Sorry Harouna, I should have been more clear about this:

Our hosted customer CLI currently cannot run an interactive task with a confirmation prompt.

Therefore, we should use a --confirm option for this, rather than defaulting to a prompt they can't see or respond to, and requiring them to use the scary word --force to succeed.

Support for interactive tasks is on my to-do list but it may be a while.