Add rich text editor

[ingoau]

Summary by CodeRabbit

• New Features

  • Introduced a rich text editor tool with advanced editing controls.
  • Updated sidebar navigation to present the new editor and automatically redirect from the previous simple text interface.

• Style

  • Enhanced typography styling for improved content presentation.

• Chores

  • Streamlined internal build processes by removing outdated automation steps.
  • Updated library versions and added new dependencies to bolster functionality and styling.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request removes screenshot-related steps from the build workflow by renaming it and deleting steps that ran a preview server, captured a screenshot, and uploaded an artifact. It adjusts dependency versions by downgrading several packages in package.json while adding new ones, including Tipex and a typography library. The Tailwind CSS configuration and the main stylesheet are updated to include typography support. Finally, the sidebar now lists a rich text editor instead of a simple text editor, with the old simple editor route now redirecting to the new rich text editor page.

Changes

File(s)	Change Summary
.github/workflows/build.yml	Renamed workflow from "Build and Screenshot" to "Build" and removed all screenshot and upload steps.
package.json, tailwind.config.ts	Downgraded dependency versions (@sveltejs/kit, bits-ui, prettier, svelte) and added new dependencies (@friendofsvelte/tipex, @tailwindcss/typography); updated Tailwind config to include the typography plugin.
src/app.css	Added directive for Tailwind CSS typography plugin (@plugin "@tailwindcss/typography";).
src/lib/components/app-sidebar.svelte, src/routes/tools/rich-text-editor/+page.svelte, src/routes/tools/simple-text-editor/+page.svelte, src/routes/tools/simple-text-editor/+page.ts	Removed "Simple Text Editor" navigation entry and page; added a new rich text editor component; established a redirection from the old simple text editor route to the rich text editor.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant R as Router
    participant E as Rich Text Editor

    U->>R: Request /tools/simple-text-editor
    R-->>U: 302 Redirect to /tools/rich-text-editor
    U->>R: Request /tools/rich-text-editor
    R->>E: Render rich text editor component

Loading

Poem

I'm a bunny in the code, hopping with delight,
Seeing screenshots vanish into the night.
Dependencies dance with a graceful downgrade,
New plugins join the parade on the stage.
The simple editor hops aside for rich text so bright!
🐰💻 Hop, skip, and code on through the night!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e1e50c7 and 5593eab.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (8)

• .github/workflows/build.yml (1 hunks)
• package.json (2 hunks)
• src/app.css (1 hunks)
• src/lib/components/app-sidebar.svelte (1 hunks)
• src/routes/tools/rich-text-editor/+page.svelte (1 hunks)
• src/routes/tools/simple-text-editor/+page.svelte (0 hunks)
• src/routes/tools/simple-text-editor/+page.ts (1 hunks)
• tailwind.config.ts (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.