Fix a link to the visual editor not actually leading anywhere

[Yusyuriv]

Before this change, it tried to scroll to an element with id="/json-rpc-visual-settingstemplate-editor" on the same page. Now it correctly leads to the visual editor page. The link in the sidebar is correct, so no changes necessary there.

[coderabbitai]

📝 Walkthrough

Walkthrough

The document json-rpc-settings.md has been updated to improve the formatting and content clarity related to plugin settings documentation. Key changes include the modification of a link to the visual editor from a relative to an absolute path, enhancing navigation. Additionally, minor formatting adjustments have been made to YAML examples and descriptions, ensuring consistency across various input types. The overall structure of the document remains unchanged, with no significant alterations to logic or control flow.

Changes

File	Change Summary
json-rpc-settings.md	Updated link to visual editor (relative to absolute path); minor formatting adjustments in YAML examples and descriptions for consistency.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation
    User->>Documentation: Access json-rpc-settings.md
    Documentation->>User: Display updated content
    User->>Documentation: Click link to visual editor
    Documentation->>User: Navigate to /json-rpc-visual-settingstemplate-editor.md

Loading

🐰 "In the garden of settings, so neat and bright,
Links now lead clearly, a navigational delight.
YAML examples, all tidy and clear,
Plugin configurations, come gather near!
With each little change, we hop with glee,
A well-structured guide for you and me!" 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 88e197a and d81ac02.

📒 Files selected for processing (1)

• json-rpc-settings.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• json-rpc-settings.md

---

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.