feat(fluent-editor): add format painter

[kagol]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Added 'undo', 'redo', 'clean', and 'format-painter' buttons to the toolbar for enhanced text editing capabilities.

• Style

  • Improved visual consistency of SVG icons by setting their width to 16 pixels.

• Chores

  • Updated the @opentiny/fluent-editor package to version ~3.19.0 for potential new features and improvements.

[coderabbitai]

Walkthrough

The pull request introduces enhancements to the Fluent Editor by modifying the toolbar configuration to include additional editing buttons: 'undo', 'redo', 'clean', and 'format-painter'. It also updates the CSS for SVG icons to ensure consistent sizing and adjusts the version of the @opentiny/fluent-editor dependency in the package.json file.

Changes

Files	Change Summary
examples/sites/demos/pc/app/fluent-editor/options-composition-api.vue, examples/sites/demos/pc/app/fluent-editor/options.vue	Added ['undo', 'redo', 'clean', 'format-painter'] to the toolbar array in the options object.
packages/theme/src/fluent-editor/index.less	Added width: 16px; to svg elements for improved visual consistency.
packages/vue/src/fluent-editor/package.json	Updated @opentiny/fluent-editor version from ~3.18.0 to ~3.19.0.

Possibly related PRs

• fix(fluent-editor): fix link and img render error #2142: This PR addresses rendering errors in the fluent editor, which may relate to the overall functionality and user experience improvements being made in the main PR, particularly in enhancing the toolbar's capabilities.

Suggested reviewers

• zzcr
• jdoe
• asmith

🐰 In the editor's bright space,
New buttons find their place.
Undo, redo, clean with flair,
Format-painter shows we care!
With icons set to fit just right,
Editing's now a pure delight! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

examples/sites/demos/pc/app/fluent-editor/options.vue (1)

Line range hint 1-80: Update the documentation.

As new toolbar options have been added, please ensure that the documentation is updated to reflect these changes and provide usage instructions for the new features.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f0a1244 and c822d6a.

Files selected for processing (4)

• examples/sites/demos/pc/app/fluent-editor/options-composition-api.vue (1 hunks)
• examples/sites/demos/pc/app/fluent-editor/options.vue (1 hunks)
• packages/theme/src/fluent-editor/index.less (1 hunks)
• packages/vue/src/fluent-editor/package.json (1 hunks)

Files skipped from review due to trivial changes (1)

• packages/theme/src/fluent-editor/index.less

Additional comments not posted (2)

packages/vue/src/fluent-editor/package.json (1)

14-14: Verify the application with the newer version of @opentiny/fluent-editor.

The version bump of @opentiny/fluent-editor from ~3.18.0 to ~3.19.0 looks good. However, it's important to verify that the application still works as expected with the newer version, especially if there are any breaking changes.

Run the following script to verify the application:

If any of the tests fail or if there are any breaking changes or issues found, please investigate and fix them before merging this PR.

examples/sites/demos/pc/app/fluent-editor/options-composition-api.vue (1)

19-19: LGTM! The new toolbar buttons enhance the text editing capabilities.

The addition of 'undo', 'redo', 'clean', and 'format-painter' buttons to the toolbar configuration is a great enhancement. These buttons will provide users with more comprehensive text manipulation options, improving the overall user experience.

The 'format-painter' button, in particular, aligns perfectly with the primary objective of this PR, which is to introduce a format painter feature. This feature will enable users to easily apply formatting from one part of the text to another, streamlining the editing process.

The changes are limited to the toolbar configuration and do not introduce any breaking changes. The code segment is syntactically correct and follows the existing code structure.

Great work on this enhancement!