PCH Smart Linking: Update link setting labels for accuracy

[acicovic]

Description

This PR updates the link setting labels of our PCH Smart Linking feature to be more accurate regarding their functionality.

Motivation and context

Make clear that the specified numbers are a target/approximation, not an absolute value.

How has this been tested?

• Existing tests pass.
• Manually verified that the label text has been updated.

Summary by CodeRabbit

• New Features
  • Updated labels in the Smart Linking settings for clarity: "Max Number of Links" to "Target Number of Links" and "Max Link Length" to "Target Link Length".

[coderabbitai]

Walkthrough

Walkthrough

The update focuses on modifying terminology within the SmartLinkingSettings component. Specifically, it involves changing the labels for settings related to the number and length of links. The terms "Max Number of Links" and "Max Link Length" are updated to "Target Number of Links" and "Target Link Length," respectively, to better reflect their intended functionality.

Changes

File Path	Change Summary
.../smart-linking/component-settings.tsx	Renamed labels from "Max Number of Links" to "Target Number of Links" and from "Max Link Length" to "Target Link Length".

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: .coderabbit.yaml

Commits

Files that changed from the base of the PR and between d0095de and aff0f1c.

Files ignored due to path filters (2)

• build/content-helper/editor-sidebar.asset.php is excluded by !build/**
• build/content-helper/editor-sidebar.js is excluded by !build/**

Files selected for processing (1)

• src/content-helper/editor-sidebar/smart-linking/component-settings.tsx (2 hunks)

Path instructions used (1)

src/content-helper/editor-sidebar/smart-linking/component-settings.tsx (1)

**/*.{js,ts,tsx,jsx}
Perform a detailed review of the provided code with following key aspects in mind:

• Review the code to ensure it is well-structured and adheres to best practices.
• Verify compliance with WordPress coding standards.
• Ensure the code is well-documented.
• Check for security vulnerabilities and confirm the code is secure.
• Optimize the code for performance, removing any unnecessary elements.
• Validate JSDoc comments for accuracy, currency, and adherence to WordPress coding standards.
• Ensure each line comment concludes with a period.
• Confirm every JSDoc comment includes a @SInCE tag indicating the next version of the plugin to include the code.
• Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features.

Additional comments (2)

src/content-helper/editor-sidebar/smart-linking/component-settings.tsx (2)

• 228-228: The label change from "Max Number of Links" to "Target Number of Links" aligns with the PR objectives to set the right user expectations. Ensure that this change is reflected in user documentation and any related UI elements for consistency.
• 241-241: The label change from "Max Link Length" to "Target Link Length" is consistent with the PR's goal of clarifying that these settings are targets rather than strict limits. Similar to the previous comment, verify that this update is consistently applied across all user-facing materials.