Fix some Content Helper strings to Content Intelligence#3520
Fix some Content Helper strings to Content Intelligence#3520
Conversation
acicovic
added
the
Maintenance & Fixes
📝 WalkthroughWalkthroughThis change systematically renames all references to "Content Helper" as "Content Intelligence" throughout the codebase, documentation, user interface, comments, and tests. Only terminology, URLs, and related labels are updated; no functional, logical, or structural code changes are introduced. Changes
Sequence Diagram(s)Not applicable: No control flow or feature logic changes were made. Possibly related PRs
Suggested labels
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 PHPStan (2.1.15)Note: Using configuration file /phpstan.neon. 🔧 ESLint
npm error Exit handler never called! ✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🔭 Outside diff range comments (2)
src/content-helper/common/content-helper-error.tsx (1)
198-200: HTML string should use ‘class’ not ‘className’.
Inside a plain HTML string React won’t translateclassName; browsers will render the literal attribute.-return `<p className="content-helper-error-message-hint" data-testid="content-helper-error-message-hint"><strong>${ __( 'Hint:', 'wp-parsely' ) }</strong> ${ hint }</p>`; +return `<p class="content-helper-error-message-hint" data-testid="content-helper-error-message-hint"><strong>${ __( 'Hint:', 'wp-parsely' ) }</strong> ${ hint }</p>`;src/js/admin-settings.ts (1)
223-240: Hard-coded selector still uses the old class in one place.
baseSelectorcorrectly switched to.content-intelligence-section, yet the notice DIV created below (line 293) is still given classcontent-helper-message, causing styles not to apply.-const baseSelector = '.wp-admin .content-intelligence-section fieldset'; +const baseSelector = '.wp-admin .content-intelligence-section fieldset'; ... -div.className = 'content-helper-message notice notice-error'; +div.className = 'content-intelligence-message notice notice-error';
🧹 Nitpick comments (23)
src/content-helper/common/utils/permissions.ts (2)
1-5: DocBlock updated, interface name now inconsistent with wording.
Consider renamingContentHelperPermissions(and the backing globalwpParselyContentHelperPermissions) to something that includes “Intelligence” for long-term clarity.
I realise this PR is intentionally textual; treat this as a future-proofing note.
28-33: AvoidJSON.parseonundefined.
Ifwindow.wpParselyContentHelperPermissionsis not defined,JSON.parsewill throw only to be swallowed by thecatch, incurring unnecessary work. A cheap guard avoids that:-const permissions = JSON.parse( window.wpParselyContentHelperPermissions ); +if ( typeof window.wpParselyContentHelperPermissions !== 'string' ) { + return defaultPermissions; +} +const permissions = JSON.parse( window.wpParselyContentHelperPermissions );src/content-helper/common/content-helper-error.tsx (1)
106-110: Link still points to “content-helper” slug.
With the rebrand, update the URL fragment to avoid sending users to an outdated anchor.-'<a href="https://wpvip.com/content-helper/#content-helper-form" target="_blank" rel="noopener">here</a>.' +'<a href="https://wpvip.com/content-intelligence/#content-intelligence-form" target="_blank" rel="noopener">here</a>.'src/rest-api/settings/class-endpoint-traffic-boost-settings.php (1)
14-15: Docblock update is fine; check internal naming for consistency.The public-facing description now says “Content Intelligence,” but the meta-key returned in
get_meta_key()(line 41) still containscontent_helper.
If that key intentionally remains unchanged for backward compatibility, consider dropping a short inline comment to make the rationale explicit; otherwise, you may want to schedule a follow-up migration to keep internal and external terminology in sync.tests/Integration/RestAPI/ContentHelper/ContentHelperControllerTest.php (1)
3-3: Header renamed, but the test namespace still readsContentHelper.No change requested right now, just a heads-up: if the classes themselves ever get re-namespaced to “Content Intelligence,” the test path and
namespacedeclaration (line 11) will need to follow suit to avoid autoloading issues.src/rest-api/settings/class-endpoint-editor-sidebar-settings.php (1)
14-15: Docblock wording aligned; add clarification on legacy keys.Same as the Traffic-Boost endpoint: the updated wording is correct, but
get_meta_key()(line 42) still usescontent_helper.
Either annotate the method explaining why the legacy key is retained, or plan a migration/alias so future developers are not confused.src/rest-api/content-helper/trait-content-helper-feature.php (1)
3-6: Docblock branding fixed; consider longer-term rename of the trait itself.The trait/class names (
Content_Helper_Feature, namespace path, and error codes likech_access_to_feature_disabled) still carry the old prefix.
Refactoring these identifiers would be a bigger-bang change, so no action required in this PR, but keep it on the radar to avoid a split vocabulary in the codebase.Also applies to: 20-22
src/rest-api/settings/class-endpoint-dashboard-widget-settings.php (1)
14-15: DocBlock rename looks good, but meta-key still references “content_helper”.The public description now says “Content Intelligence,” yet
get_meta_key()still returns'parsely_content_helper_settings_dashboard_widget'. Consider whether a follow-up migration/alias is needed to avoid branding drift in stored options.tests/Integration/UI/SettingsPageTest.php (1)
740-742: DocBlock updated; method name still uses “pch”.While the description now says “Content Intelligence options,” the helper is still named
transform_pch_options_for_validation, and it populates the'content_helper'array. Ensure this dual terminology is intentional; otherwise consider renaming for consistency.src/rest-api/content-helper/class-endpoint-traffic-boost.php (1)
4-5: Add terminating period to class-level summary.Per WordPress PHPDoc standards, the summary line should end with a period.
- * Parse.ly Content Intelligence `/traffic-boost` API endpoint class + * Parse.ly Content Intelligence `/traffic-boost` API endpoint class.src/UI/class-dashboard-page.php (1)
329-341: Method name now misleading—consider renaming.The docblock now references “Content Intelligence,” but the method is still named
inject_content_helper_permissions(), which can confuse readers and future maintainers.- protected function inject_content_helper_permissions(): void { + protected function inject_content_intelligence_permissions(): void {You’d also need to update the call at line 288 and the JS global set at 340.
src/content-helper/editor-sidebar/tabs/sidebar-performance-tab.tsx (1)
22-23: Minor casing inconsistency.In the Tools tab file the word “sidebar” is lowercase, here it’s capitalized. Aligning casing keeps docs uniform.
- * Renders the Performance tab in the Content Intelligence Sidebar. + * Renders the Performance tab in the Content Intelligence sidebar.docs/TESTING.md (1)
125-128: Grammar fix for bullet point.Plural subject “Stats” should use “appear,” and initial article can be lowercase.
- - Check that The Content Intelligence Post List Stats appears + - Check that the Content Intelligence Post List Stats appearsrc/content-helper/editor-sidebar/editor-sidebar.tsx (1)
193-198: Optional: align component name with the new branding.The JSDoc now refers to “Content Intelligence Editor Sidebar”, but the exported component is still named
ContentHelperEditorSidebar.
If a broader rename is planned, consider renaming the component (and its import paths/usages) for complete consistency.src/content-helper/editor-sidebar/excerpt-suggestions/class-excerpt-suggestions.php (2)
3-7: Add trailing periods to satisfy WP docs guideline.Several summary lines end without a period, which diverges from the project’s documented convention for PHPDoc lines.
- * Content Intelligence: Excerpt Suggestions feature class + * Content Intelligence: Excerpt Suggestions feature class. ... - * Content Intelligence: Excerpt Suggestions feature class + * Content Intelligence: Excerpt Suggestions feature class.Also applies to: 16-20
104-108: Minor wording & punctuation tweak.Consider ending the sentence with a period for consistency:
- * Inserts Content Intelligence Excerpt Suggestions inline scripts. + * Inserts Content Intelligence Excerpt Suggestions inline scripts.tests/e2e/specs/activation-flow.spec.ts (1)
60-63: Consider renaming the “contentHelper…” locators to match the new terminology.The locator variables (
contentHelperTab,contentHelperSection) still carry the legacy “Helper” wording, while the visible-text and CSS class have been updated to “Content Intelligence”.
Renaming these variables will keep terminology consistent and improve readability.-const contentHelperTab = page.getByRole( 'link', { name: 'Content Intelligence' } ); -const contentHelperSection = page.locator( '.content-intelligence-section' ); +const contentIntelligenceTab = page.getByRole( 'link', { name: 'Content Intelligence' } ); +const contentIntelligenceSection = page.locator( '.content-intelligence-section' );Subsequent usages (
contentHelperSection,contentHelperTab) would need the same update.Also applies to: 86-91
tests/Integration/OptionsTest.php (4)
588-597: Method names still reference “content_helper”.The surrounding docblocks now say “Content Intelligence”, but the test method is still called
test_content_helper_options_in_a_new_plugin_install().
Renaming the method (and similar ones below) would avoid terminology drift, though it’s purely cosmetic.
623-633: Same naming inconsistency as above.
665-675: Same naming inconsistency as above.
701-709: Same naming inconsistency as above.src/js/admin-settings.ts (1)
73-83: Function name no longer matches the feature’s new branding.The docblock now references “Content Intelligence,” but the function is still called
addContentHelperTabEventHandlers(). Keeping the old “ContentHelper” wording can cause confusion for future readers and makes grepping for the new feature harder.-function addContentHelperTabEventHandlers(): void { +function addContentIntelligenceTabEventHandlers(): void {Remember to update the
DOMContentLoadedcallback at line 16 accordingly.src/class-parsely.php (1)
688-702: Method name diverges from updated terminology.The docblock now says “Sets the default values for Content Intelligence options,” yet the method is still named
set_default_content_helper_settings_values(). Consider renaming for consistency; otherwise newcomers may assume two separate concepts exist.Refactor only if you can guarantee all callers (including tests) are updated.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (2)
build/admin-settings.asset.phpis excluded by!build/**build/admin-settings.jsis excluded by!build/**
📒 Files selected for processing (40)
CHANGELOG.md(1 hunks)README.md(1 hunks)docs/TESTING.md(1 hunks)src/UI/class-dashboard-page.php(1 hunks)src/UI/class-settings-page.php(5 hunks)src/class-parsely.php(2 hunks)src/class-permissions.php(4 hunks)src/content-helper/common/class-content-helper-feature.php(5 hunks)src/content-helper/common/content-helper-error.tsx(2 hunks)src/content-helper/common/css/common.scss(1 hunks)src/content-helper/common/utils/constants.ts(3 hunks)src/content-helper/common/utils/permissions.ts(2 hunks)src/content-helper/editor-sidebar/class-editor-sidebar-feature.php(1 hunks)src/content-helper/editor-sidebar/editor-sidebar.tsx(1 hunks)src/content-helper/editor-sidebar/excerpt-suggestions/class-excerpt-suggestions.php(3 hunks)src/content-helper/editor-sidebar/related-posts/component.tsx(1 hunks)src/content-helper/editor-sidebar/tabs/sidebar-performance-tab.tsx(1 hunks)src/content-helper/editor-sidebar/tabs/sidebar-tools-tab.tsx(1 hunks)src/js/admin-settings.ts(6 hunks)src/rest-api/content-helper/class-content-helper-controller.php(3 hunks)src/rest-api/content-helper/class-endpoint-check-auth.php(2 hunks)src/rest-api/content-helper/class-endpoint-excerpt-generator.php(2 hunks)src/rest-api/content-helper/class-endpoint-smart-linking.php(2 hunks)src/rest-api/content-helper/class-endpoint-title-suggestions.php(2 hunks)src/rest-api/content-helper/class-endpoint-traffic-boost.php(2 hunks)src/rest-api/content-helper/trait-content-helper-feature.php(2 hunks)src/rest-api/settings/class-endpoint-dashboard-widget-settings.php(1 hunks)src/rest-api/settings/class-endpoint-editor-sidebar-settings.php(1 hunks)src/rest-api/settings/class-endpoint-traffic-boost-settings.php(1 hunks)tests/Integration/ContentHelper/ContentHelperDashboardWidgetTest.php(2 hunks)tests/Integration/ContentHelper/ContentHelperFeatureTest.php(16 hunks)tests/Integration/ContentHelper/ContentHelperPostListStatsTest.php(2 hunks)tests/Integration/OptionsTest.php(4 hunks)tests/Integration/PermissionsTest.php(8 hunks)tests/Integration/RestAPI/ContentHelper/ContentHelperControllerTest.php(1 hunks)tests/Integration/RestAPI/ContentHelper/ContentHelperFeatureTestTrait.php(2 hunks)tests/Integration/UI/SettingsPageTest.php(1 hunks)tests/e2e/specs/activation-flow.spec.ts(2 hunks)tests/e2e/utils.ts(1 hunks)tests/js/content-helper/content-helper-error.test.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
`**/*.{html,php}`: "Perform a detailed review of the provided code with followin...
**/*.{html,php}: "Perform a detailed review of the provided code with following key aspects in mind:
- Review the HTML and PHP code to ensure it is well-structured and adheres to best practices.
- Ensure the code follows WordPress coding standards and is well-documented.
- Confirm the code is secure and free from vulnerabilities.
- Optimize the code for performance, removing any unnecessary elements.
- Validate comments for accuracy, currency, and adherence to WordPress coding standards.
- Ensure each line comment concludes with a period.
- Verify code compatibility with the latest version of WordPress, avoiding deprecated functions or features."
⚙️ Source: CodeRabbit Configuration File
List of files the instruction was applied to:
src/rest-api/settings/class-endpoint-editor-sidebar-settings.phpsrc/rest-api/content-helper/trait-content-helper-feature.phpsrc/rest-api/settings/class-endpoint-traffic-boost-settings.phpsrc/rest-api/content-helper/class-endpoint-title-suggestions.phptests/Integration/RestAPI/ContentHelper/ContentHelperControllerTest.phpsrc/rest-api/settings/class-endpoint-dashboard-widget-settings.phpsrc/UI/class-dashboard-page.phpsrc/rest-api/content-helper/class-endpoint-traffic-boost.phpsrc/rest-api/content-helper/class-endpoint-check-auth.phpsrc/content-helper/editor-sidebar/excerpt-suggestions/class-excerpt-suggestions.phptests/Integration/UI/SettingsPageTest.phpsrc/content-helper/editor-sidebar/class-editor-sidebar-feature.phptests/Integration/ContentHelper/ContentHelperDashboardWidgetTest.phpsrc/rest-api/content-helper/class-content-helper-controller.phptests/Integration/RestAPI/ContentHelper/ContentHelperFeatureTestTrait.phptests/Integration/PermissionsTest.phptests/Integration/OptionsTest.phpsrc/content-helper/common/class-content-helper-feature.phpsrc/class-parsely.phpsrc/rest-api/content-helper/class-endpoint-smart-linking.phpsrc/rest-api/content-helper/class-endpoint-excerpt-generator.phptests/Integration/ContentHelper/ContentHelperFeatureTest.phptests/Integration/ContentHelper/ContentHelperPostListStatsTest.phpsrc/class-permissions.phpsrc/UI/class-settings-page.php
`**/*.{js,ts,tsx,jsx}`: "Perform a detailed review of the provided code with fol...
**/*.{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."
⚙️ Source: CodeRabbit Configuration File
List of files the instruction was applied to:
tests/js/content-helper/content-helper-error.test.tssrc/content-helper/common/content-helper-error.tsxsrc/content-helper/editor-sidebar/tabs/sidebar-tools-tab.tsxsrc/content-helper/editor-sidebar/tabs/sidebar-performance-tab.tsxsrc/content-helper/common/utils/constants.tstests/e2e/utils.tssrc/content-helper/common/utils/permissions.tssrc/content-helper/editor-sidebar/editor-sidebar.tsxsrc/content-helper/editor-sidebar/related-posts/component.tsxsrc/js/admin-settings.tstests/e2e/specs/activation-flow.spec.ts
`**/*.{css,scss}`: "Perform a detailed review of the provided code with followin...
**/*.{css,scss}: "Perform a detailed review of the provided code with following key aspects in mind:
- Review the SCSS code to ensure it is well-structured and adheres to best practices.
- Convert dimensions greater than or equal to 3px to rem units using the to_rem function.
- Utilize variables for sizes and colors defined in src/content-helper/common/css/variables.scss instead of hardcoding values."
⚙️ Source: CodeRabbit Configuration File
List of files the instruction was applied to:
src/content-helper/common/css/common.scss
🧠 Learnings (25)
📓 Common learnings
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
Learnt from: acicovic
PR: Parsely/wp-parsely#2554
File: src/UI/class-settings-page.php:28-29
Timestamp: 2024-06-18T09:33:19.519Z
Learning: acicovic prefers to use the term "resolve" to indicate that an issue or request has been addressed satisfactorily.
Learnt from: acicovic
PR: Parsely/wp-parsely#2554
File: src/UI/class-settings-page.php:28-29
Timestamp: 2024-10-12T10:01:08.699Z
Learning: acicovic prefers to use the term "resolve" to indicate that an issue or request has been addressed satisfactorily.
src/rest-api/content-helper/class-endpoint-title-suggestions.php (1)
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
docs/TESTING.md (4)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The "Tested up to:" line in the `README.md` file of WordPress plugins follows a specific format as per the WordPress.org documentation and should not be altered based on grammatical considerations.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The "Tested up to:" line in the `README.md` file of WordPress plugins follows a specific format as per the WordPress.org documentation and should not be altered based on grammatical considerations.
src/UI/class-dashboard-page.php (1)
Learnt from: alecgeatches
PR: Parsely/wp-parsely#3482
File: src/content-helper/dashboard-page/pages/dashboard/header-component.tsx:93-93
Timestamp: 2025-06-24T17:27:48.332Z
Learning: The dashboard page in src/content-helper/dashboard-page/pages/dashboard/header-component.tsx currently contains static labels and data and is not in use anywhere. Translation work for this page can be deferred until it contains real data and is actively used.
src/content-helper/editor-sidebar/tabs/sidebar-tools-tab.tsx (2)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
src/content-helper/common/css/common.scss (1)
Learnt from: acicovic
PR: Parsely/wp-parsely#3064
File: src/content-helper/common/css/variables.scss:94-94
Timestamp: 2025-01-14T09:27:47.106Z
Learning: In src/content-helper/common/css/variables.scss, direct `rem` units are used instead of the `to_rem` function for dimensions.
src/content-helper/editor-sidebar/tabs/sidebar-performance-tab.tsx (4)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: alecgeatches
PR: Parsely/wp-parsely#3482
File: src/content-helper/dashboard-page/pages/dashboard/header-component.tsx:93-93
Timestamp: 2025-06-24T17:27:48.332Z
Learning: The dashboard page in src/content-helper/dashboard-page/pages/dashboard/header-component.tsx currently contains static labels and data and is not in use anywhere. Translation work for this page can be deferred until it contains real data and is actively used.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
src/content-helper/common/utils/constants.ts (3)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/tabs/sidebar-tools-tab.tsx:5-5
Timestamp: 2024-10-09T07:53:49.520Z
Learning: `PostTypeSupportCheck` should be imported from `@wordpress/editor`, following the official WordPress documentation.
src/content-helper/editor-sidebar/excerpt-suggestions/class-excerpt-suggestions.php (4)
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
Learnt from: vaurdan
PR: Parsely/wp-parsely#2890
File: src/content-helper/editor-sidebar/editor-sidebar.tsx:283-286
Timestamp: 2024-10-25T12:52:20.502Z
Learning: The Excerpt Suggestions need to be initialized before the DOM loads, so it should not be wrapped in domReady().
Learnt from: vaurdan
PR: Parsely/wp-parsely#2507
File: src/content-helper/editor-sidebar/smart-linking/utils.ts:461-531
Timestamp: 2024-10-12T10:01:08.699Z
Learning: Content from Gutenberg blocks is sanitized by WordPress before storage, minimizing the risk of XSS when such content is processed further in functions like `validateAndFixSmartLinks`.
Learnt from: vaurdan
PR: Parsely/wp-parsely#2507
File: src/content-helper/editor-sidebar/smart-linking/utils.ts:461-531
Timestamp: 2024-07-26T21:07:21.167Z
Learning: Content from Gutenberg blocks is sanitized by WordPress before storage, minimizing the risk of XSS when such content is processed further in functions like `validateAndFixSmartLinks`.
tests/e2e/utils.ts (2)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
tests/Integration/UI/SettingsPageTest.php (2)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
src/content-helper/common/utils/permissions.ts (2)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
src/content-helper/editor-sidebar/editor-sidebar.tsx (3)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
src/content-helper/editor-sidebar/class-editor-sidebar-feature.php (1)
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
src/content-helper/editor-sidebar/related-posts/component.tsx (10)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The `onClick` function in `PerformanceStatsMenu` component of `src/content-helper/editor-sidebar/performance-stats/component.tsx` is documented with a JSDoc comment.
Learnt from: vaurdan
PR: Parsely/wp-parsely#3064
File: src/content-helper/common/components/snackbar-notices/component.tsx:0-0
Timestamp: 2025-01-16T11:14:54.541Z
Learning: When using `useSelect` hook with WordPress's `noticesStore`, an empty dependency array is sufficient since the store reference is constant and doesn't change between renders.
Learnt from: acicovic
PR: Parsely/wp-parsely#3293
File: src/content-helper/dashboard-page/components/posts-table/components/post-details.tsx:24-36
Timestamp: 2025-05-08T11:26:10.195Z
Learning: The PostDetails component should use the `getSmartShortDate()` function from '../../../../common/utils/date' rather than the WordPress format function for formatting dates. This provides better localization support and intelligent formatting that adapts to whether the date is in the current year.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
Learnt from: vaurdan
PR: Parsely/wp-parsely#2430
File: src/content-helper/editor-sidebar/smart-linking/component.tsx:448-450
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The `originalContent` property may not be present in certain WordPress block types like the Group block, making it necessary to check for its existence before using `getBlockContent`.
Learnt from: vaurdan
PR: Parsely/wp-parsely#2430
File: src/content-helper/editor-sidebar/smart-linking/component.tsx:448-450
Timestamp: 2024-10-12T10:01:08.699Z
Learning: The `originalContent` property may not be present in certain WordPress block types like the Group block, making it necessary to check for its existence before using `getBlockContent`.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/tabs/sidebar-tools-tab.tsx:5-5
Timestamp: 2024-10-09T07:53:49.520Z
Learning: `PostTypeSupportCheck` should be imported from `@wordpress/editor`, following the official WordPress documentation.
Learnt from: acicovic
PR: Parsely/wp-parsely#2841
File: src/@types/gutenberg/types.ts:60-60
Timestamp: 2024-10-08T13:03:44.802Z
Learning: In `src/@types/gutenberg/types.ts`, the double type assertion `as unknown as GutenbergCoreEditorFunction` is necessary for `dispatchCoreEditor` because TypeScript complains due to the types not overlapping.
Learnt from: acicovic
PR: Parsely/wp-parsely#2841
File: src/@types/gutenberg/types.ts:60-60
Timestamp: 2024-10-12T10:01:08.699Z
Learning: In `src/@types/gutenberg/types.ts`, the double type assertion `as unknown as GutenbergCoreEditorFunction` is necessary for `dispatchCoreEditor` because TypeScript complains due to the types not overlapping.
src/js/admin-settings.ts (3)
Learnt from: alecgeatches
PR: Parsely/wp-parsely#3482
File: src/content-helper/dashboard-page/pages/dashboard/header-component.tsx:93-93
Timestamp: 2025-06-24T17:27:48.332Z
Learning: The dashboard page in src/content-helper/dashboard-page/pages/dashboard/header-component.tsx currently contains static labels and data and is not in use anywhere. Translation work for this page can be deferred until it contains real data and is actively used.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
Learnt from: alecgeatches
PR: Parsely/wp-parsely#3293
File: src/content-helper/dashboard-page/components/posts-table/components/post-details.tsx:36-41
Timestamp: 2025-05-08T19:06:14.641Z
Learning: In WordPress plugins, using `dangerouslySetInnerHTML` with content from WordPress API (like `post.title.rendered`) can be acceptable since WordPress pre-escapes this content. This allows HTML entities to render correctly while maintaining security due to WordPress's built-in sanitization.
tests/Integration/PermissionsTest.php (2)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
tests/Integration/OptionsTest.php (4)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: The "Tested up to:" line in the `README.md` file of WordPress plugins follows a specific format as per the WordPress.org documentation and should not be altered based on grammatical considerations.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: The "Tested up to:" line in the `README.md` file of WordPress plugins follows a specific format as per the WordPress.org documentation and should not be altered based on grammatical considerations.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
src/content-helper/common/class-content-helper-feature.php (1)
Learnt from: acicovic
PR: Parsely/wp-parsely#2942
File: src/UI/class-dashboard-page.php:177-187
Timestamp: 2024-11-13T14:14:42.961Z
Learning: The `get_pch_permissions_json()` function uses `wp_json_encode()`, ensuring that permissions JSON data is properly escaped before being injected into JavaScript.
src/rest-api/content-helper/class-endpoint-smart-linking.php (2)
Learnt from: vaurdan
PR: Parsely/wp-parsely#2507
File: src/content-helper/editor-sidebar/smart-linking/provider.ts:80-88
Timestamp: 2024-07-26T21:07:21.167Z
Learning: Error handling for API calls in the `SmartLinkingProvider` class is managed by the Provider base class.
Learnt from: vaurdan
PR: Parsely/wp-parsely#2507
File: src/content-helper/editor-sidebar/smart-linking/provider.ts:80-88
Timestamp: 2024-10-12T10:01:08.699Z
Learning: Error handling for API calls in the `SmartLinkingProvider` class is managed by the Provider base class.
src/rest-api/content-helper/class-endpoint-excerpt-generator.php (1)
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
README.md (1)
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
CHANGELOG.md (3)
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355
Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.
Learnt from: acicovic
PR: Parsely/wp-parsely#2811
File: src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx:282-285
Timestamp: 2024-10-09T07:42:35.719Z
Learning: When linking to official WordPress documentation in `src/content-helper/editor-sidebar/excerpt-suggestions/component-panel.tsx`, wrapping URLs with the translation function `__()` is appropriate to allow localization to non-English documentation pages.
src/class-permissions.php (1)
Learnt from: acicovic
PR: Parsely/wp-parsely#2942
File: src/UI/class-dashboard-page.php:177-187
Timestamp: 2024-11-13T14:14:42.961Z
Learning: The `get_pch_permissions_json()` function uses `wp_json_encode()`, ensuring that permissions JSON data is properly escaped before being injected into JavaScript.
src/UI/class-settings-page.php (2)
Learnt from: vaurdan
PR: Parsely/wp-parsely#2507
File: src/content-helper/editor-sidebar/smart-linking/utils.ts:461-531
Timestamp: 2024-10-12T10:01:08.699Z
Learning: Content from Gutenberg blocks is sanitized by WordPress before storage, minimizing the risk of XSS when such content is processed further in functions like `validateAndFixSmartLinks`.
Learnt from: vaurdan
PR: Parsely/wp-parsely#2507
File: src/content-helper/editor-sidebar/smart-linking/utils.ts:461-531
Timestamp: 2024-07-26T21:07:21.167Z
Learning: Content from Gutenberg blocks is sanitized by WordPress before storage, minimizing the risk of XSS when such content is processed further in functions like `validateAndFixSmartLinks`.
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: build
- GitHub Check: E2E against WordPress latest
- GitHub Check: build
🔇 Additional comments (27)
src/content-helper/common/css/common.scss (1)
14-16: Comment rename looks good.
No functional impact; terminology is now consistent with the rest of the PR.src/content-helper/common/utils/constants.ts (1)
9-15: Pure comment change – OK.
Terminology aligns; no code impact.Also applies to: 25-31, 36-41
tests/js/content-helper/content-helper-error.test.ts (1)
57-59: Test description update confirmed.
Label now reflects new branding; assertion logic unchanged.src/content-helper/editor-sidebar/class-editor-sidebar-feature.php (1)
67-68: Inline comment updated — looks good.No further issues found in this file.
tests/e2e/utils.ts (1)
57-59: Updated sidebar wording, but CSS selectors remain on the old prefix.The comment now says “Content Intelligence,” yet the selectors (
.content-helper-error-message,.wp-parsely-content-helper …) still embed “content-helper”. If the CSS classes are intended to change in the UI, the tests will break—please confirm the classes stay as-is for backward compatibility or update the selectors accordingly.src/rest-api/content-helper/class-endpoint-check-auth.php (1)
4-4: DocBlock branding updated—implementation namespace unchanged.Comments now read “Content Intelligence,” but the file path & namespace remain
content-helper. That’s fine for backward compatibility, just confirm this split won’t confuse future contributors or tooling.Also applies to: 43-44
src/rest-api/content-helper/class-endpoint-title-suggestions.php (1)
4-4: DocBlock branding aligned; code untouched—good.No functional impact; the rename is clear and consistent with other endpoints.
Also applies to: 44-45
src/content-helper/editor-sidebar/tabs/sidebar-tools-tab.tsx (1)
31-32: JSDoc update looks good.The wording change is accurate, ends with a period, and keeps the
@sincetag intact. No further action needed.src/rest-api/content-helper/class-endpoint-traffic-boost.php (1)
49-51: Docblock parameter line LGTM.Description correctly updated and ends with a period.
CHANGELOG.md (1)
12-12: Changelog entry update looks correct.The URL is now fully-qualified and the bullet remains capitalized, matching the project’s conventions. No further action required.
tests/Integration/ContentHelper/ContentHelperDashboardWidgetTest.php (1)
123-124: @group annotations are consistent across the suiteNo remaining
@group content-helperentries were found when searching the test directory:
- Executed
rg --line-number '@group\s+content-helper'acrosstests/→ no matchesThe renaming to
@group content-intelligenceis applied uniformly.src/rest-api/content-helper/class-endpoint-excerpt-generator.php (1)
4-5: Docblock rename only—implementation untouched.Comment updates correctly reflect the new branding; no code changes introduced. Implementation remains unaffected.
Also applies to: 44-46
src/content-helper/editor-sidebar/related-posts/component.tsx (1)
179-181: Comment rename acknowledged.Only the inline comment was updated; logic is unchanged. No issues spotted.
tests/Integration/ContentHelper/ContentHelperPostListStatsTest.php (1)
141-142: Terminology update looks good.DocBlock
@groupannotations have been consistently renamed; no issues spotted.Also applies to: 168-169
tests/Integration/RestAPI/ContentHelper/ContentHelperFeatureTestTrait.php (1)
3-7: Consistent branding change – no action needed.The updated docblocks correctly adopt the new “Content Intelligence” wording while preserving metadata.
Also applies to: 18-24
tests/Integration/PermissionsTest.php (1)
38-50: Terminology update verified.All comment changes accurately reflect the new feature name; nothing else altered.
Also applies to: 109-119, 145-155, 183-193, 219-229, 264-274, 299-309, 335-338
src/rest-api/content-helper/class-content-helper-controller.php (1)
36-40: Route prefix vs. branding mismatch – verify backward-compat plan.Docblocks refer to “Content Intelligence”, yet
get_route_prefix()still returns'content-helper'.
If this is intentional for backward compatibility, add a brief note (e.g.,@deprecatedor inline comment) to avoid future confusion; otherwise consider aligning the prefix.tests/Integration/ContentHelper/ContentHelperFeatureTest.php (1)
188-190: Verify PHPUnit group mappings after the rename.The
@groupannotation is nowcontent-intelligence, but the namespace (…\ContentHelper) and class file path haven’t changed.
Please ensure any CI filtering (e.g.,phpunit --group content-helper) is updated, or consider adding an additional@group content-helperuntil the migration is complete.src/content-helper/common/class-content-helper-feature.php (1)
3-7: Mixed branding in filters / globals may cause confusion.Docblocks were renamed to “Content Intelligence”, but:
- The filter string remains
wp_parsely_enable_content_helper.- The injected JS global is still
window.wpParselyContentHelperPermissions.If this is intentional for back-compat, a short inline comment would help future maintainers. Otherwise, consider aligning the identifiers to the new name in a follow-up PR.
Also applies to: 32-34, 139-146
src/rest-api/content-helper/class-endpoint-smart-linking.php (1)
4-5: Docblock updates look good.
No functional impact; comment changes are accurate and keep wording consistent.Also applies to: 50-52
src/js/admin-settings.ts (1)
279-283: Out-of-date help URL still points at “content-helper.”The rebranding effort should update external links too; otherwise users will land on a 404 or an outdated page.
- 'https://wpvip.com/content-helper/#content-helper-form' + 'https://wpvip.com/content-intelligence/#content-intelligence-form'README.md (1)
37-48: Validate newly introduced documentation links.All bullets were re-pointed to
docs.parse.ly/plugin-content-intelligence/…ordocs.wpvip.com/…. Please double-check that each target URL exists; several moved pages were previously nested undercontent-helper. Broken links in the readme harm user trust.src/class-permissions.php (1)
46-58: LGTM – comment terminology updated accurately.src/UI/class-settings-page.php (4)
112-114: Comment update looks good.Only the in-line description was rebranded; no functional impact.
940-943: DocBlock rename acknowledged.Comment only; implementation unchanged.
1313-1326: Validation section comments updated correctly.No behavioural changes; branding text now consistent.
433-439: All references tocontent-helper-sectionhave been removed
Ranrg --line-number --context 2 'content-helper-section'across the repo and found no matches. There are no remaining CSS/JS selectors or anchors using the old ID.
1 participant
Description
With this PR, we're mostly updating comment/DocBlock strings related to Content Helper to their Content Intelligence equivalents. Additionally:
content-helpertocontent-intelligence. VIP documentation will need to be updated accordingly.README.mdsince they have changed.README.md, which will make our plugin page display the feature name correctly when we make our next release.CHANGELOG.mdfrom the last release.Motivation and context
content-helpertocontent-intelligence.How has this been tested?
Summary by CodeRabbit