Fix typos

[Crabcyborg]

Related PR #1842

I'm trying to break this up a bit. The update in FrmFieldType will require deprecating a function, so I plan to handle that separately.

[coderabbitai]

Walkthrough

The series of changes made to the codebase are primarily focused on correcting typos in comments, output messages, variable and function names across multiple files. These amendments enhance the overall clarity, consistency, and readability of the code without modifying any core functionalities. Besides fixing typographical mistakes, some spelling corrections were also applied to improve documentation accuracy and programming conventions adherence.

Changes

File / Paths	Change Summary
bin/build-plugin.sh, bin/git-release.sh	Corrected typos in output messages to improve spelling accuracy.
changelog.txt, readme.txt	Corrected typos to improve readability and consistency in documentation.
classes/controllers/..., classes/helpers/...	Corrected typos in comments, variable names, and function names for clarity and consistency in various controller and helper classes.
classes/models/..., classes/views/...	Corrected typos in comments and variable names to enhance code readability.
deprecated/FrmEDD_SL_Plugin_Updater.php, stripe/models/...	Corrected typographical errors in comments.
js/formidable_admin.js	Updated comments to correct spelling errors and renamed functions and variables for consistency.
tests/cypress/e2e/..., tests/phpunit/styles/test_FrmStylesHelper.php	Fixed typos in descriptions, error messages, and test suite definitions to ensure proper spelling and improve clarity in test cases.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between abf48c3 and ed6f140.

Files selected for processing (29)

• bin/build-plugin.sh (1 hunks)
• bin/git-release.sh (1 hunks)
• changelog.txt (15 hunks)
• classes/controllers/FrmDashboardController.php (1 hunks)
• classes/controllers/FrmFieldsController.php (1 hunks)
• classes/controllers/FrmFormsController.php (5 hunks)
• classes/controllers/FrmHooksController.php (1 hunks)
• classes/controllers/FrmOverlayController.php (1 hunks)
• classes/controllers/FrmStylesController.php (1 hunks)
• classes/helpers/FrmAppHelper.php (5 hunks)
• classes/helpers/FrmDashboardHelper.php (1 hunks)
• classes/helpers/FrmEntriesHelper.php (2 hunks)
• classes/helpers/FrmFieldsHelper.php (2 hunks)
• classes/models/FrmAntiSpam.php (1 hunks)
• classes/models/FrmDb.php (3 hunks)
• classes/models/FrmFieldCaptchaSettings.php (1 hunks)
• classes/models/FrmFormMigrator.php (2 hunks)
• classes/models/FrmInbox.php (1 hunks)
• classes/models/fields/FrmFieldCaptcha.php (1 hunks)
• classes/models/fields/FrmFieldType.php (1 hunks)
• classes/views/onboarding-wizard/steps/install-formidable-pro-step.php (1 hunks)
• classes/views/styles/_styles-edit.php (1 hunks)
• deprecated/FrmEDD_SL_Plugin_Updater.php (1 hunks)
• js/formidable_admin.js (4 hunks)
• readme.txt (1 hunks)
• stripe/models/FrmStrpLiteAuth.php (1 hunks)
• tests/cypress/e2e/admin-a11y.cy.js (1 hunks)
• tests/cypress/e2e/form-preview-a11y.cy.js (1 hunks)
• tests/phpunit/styles/test_FrmStylesHelper.php (2 hunks)

Files skipped from review due to trivial changes (26)

• bin/build-plugin.sh
• bin/git-release.sh
• classes/controllers/FrmDashboardController.php
• classes/controllers/FrmFieldsController.php
• classes/controllers/FrmFormsController.php
• classes/controllers/FrmHooksController.php
• classes/controllers/FrmOverlayController.php
• classes/controllers/FrmStylesController.php
• classes/helpers/FrmAppHelper.php
• classes/helpers/FrmEntriesHelper.php
• classes/helpers/FrmFieldsHelper.php
• classes/models/FrmAntiSpam.php
• classes/models/FrmDb.php
• classes/models/FrmFieldCaptchaSettings.php
• classes/models/FrmFormMigrator.php
• classes/models/FrmInbox.php
• classes/models/fields/FrmFieldCaptcha.php
• classes/models/fields/FrmFieldType.php
• classes/views/onboarding-wizard/steps/install-formidable-pro-step.php
• classes/views/styles/_styles-edit.php
• deprecated/FrmEDD_SL_Plugin_Updater.php
• js/formidable_admin.js
• stripe/models/FrmStrpLiteAuth.php
• tests/cypress/e2e/admin-a11y.cy.js
• tests/cypress/e2e/form-preview-a11y.cy.js
• tests/phpunit/styles/test_FrmStylesHelper.php

Additional context used

LanguageTool

readme.txt

[style] ~187-~187: Consider using a different verb for a more formal wording.
Context: ...P settings. 6. If these steps do not fix the problem and other WP signup emails ...

(FIX_RESOLVE)

Additional comments not posted (5)

classes/helpers/FrmDashboardHelper.php (3)

347-347: LGTM! Verify the variable usage.

The change appears to be a typo fix or a variable name correction. Ensure the variable name $wp_list_table is used consistently throughout the codebase.

Verification successful

---

LGTM! The variable $wp_list_table is used consistently throughout the codebase.

The change in classes/helpers/FrmDashboardHelper.php is correctly aligned with the rest of the codebase. There are no discrepancies or typos in the variable name usage.

• classes/helpers/FrmDashboardHelper.php
• stripe/views/lists/list.php
• stripe/controllers/FrmTransLiteListsController.php
• classes/models/FrmAddon.php
• classes/helpers/FrmAppHelper.php
• classes/views/frm-entries/list.php
• classes/views/frm-forms/list.php
• classes/views/dashboard/templates/entries-list.php
• classes/controllers/FrmEntriesController.php
• classes/controllers/FrmFormsController.php

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the variable `$wp_list_table`.

# Test: Search for the variable usage. Expect: Consistent usage of the variable name.
rg --type php $'\$wp_list_table'

Length of output: 3385

---

345-345: LGTM! Verify the variable usage.

The change appears to be a typo fix or a variable name correction. Ensure the variable name $params is used consistently throughout the codebase.

Verification successful

---

The variable usage is consistent.

The $params variable is initialized and used consistently within the classes/helpers/FrmDashboardHelper.php file.

• Initialization: FrmForm::get_admin_params()
• Usage: Passed as part of an array to a new instance of $controller_entries_table.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the variable `$params`.

# Test: Search for the variable usage. Expect: Consistent usage of the variable name.
rg --type php $'\$params'

Length of output: 16728

---

Script:

#!/bin/bash
# Description: Verify the usage of the variable `$params` specifically within the `classes/helpers/FrmDashboardHelper.php` file.

# Test: Search for the variable usage within the specific file.
rg --type php '\$params' classes/helpers/FrmDashboardHelper.php

Length of output: 217

---

346-346: LGTM! Verify the variable usage.

The change appears to be a typo fix or a variable name correction. Ensure the variable name $controller_entries_table is used consistently throughout the codebase.

Verification successful

LGTM! Verify the context around variable usage.

The variable $controller_entries_table is used consistently within the FrmDashboardHelper.php file. Ensure that the context around these lines does not introduce any issues.

---

LGTM! The variable usage is consistent and the context is appropriate.

The variable $controller_entries_table is used correctly and consistently within the FrmDashboardHelper.php file. The context around its usage does not introduce any issues.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of the variable `$controller_entries_table`.

# Test: Search for the variable usage. Expect: Consistent usage of the variable name.
rg --type php $'\$controller_entries_table'

Length of output: 312

---

Script:

#!/bin/bash
# Description: Verify the lines around the usage of the variable `$controller_entries_table` to ensure correct context and no issues.

# Extract lines around the relevant code snippets.
rg --type php -C 5 $'\$controller_entries_table' classes/helpers/FrmDashboardHelper.php

Length of output: 498

changelog.txt (2)

69-69: Fix Typo: "API requests sent for retrieving add-on and template data will now happen less frequently."

The correction improves clarity and accuracy.

---

218-218: Fix Typo: "Captcha key settings will now be trimmed on save to avoid unnecessary whitespace characters reported to cause issues in some cases."

The correction improves clarity and accuracy.

---

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 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 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 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 as 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.

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.
• 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.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

readme.txt (1)

187-187: Consider using a more formal wording.

The current wording is informal. Consider using "resolve" instead of "fix" for a more formal tone.

-    6. If these steps do not fix the problem and other WP signup emails are not going out, please reach out to your web host.
+    6. If these steps do not resolve the issue and other WP signup emails are not being sent, please contact your web host.

Tools

LanguageTool

[style] ~187-~187: Consider using a different verb for a more formal wording.
Context: ...P settings. 6. If these steps do not fix the problem and other WP signup emails ...

(FIX_RESOLVE)