Skip to content

Fix typos#1842

Closed
szepeviktor wants to merge 2 commits into
Strategy11:masterfrom
szepeviktor:typos
Closed

Fix typos#1842
szepeviktor wants to merge 2 commits into
Strategy11:masterfrom
szepeviktor:typos

Conversation

@szepeviktor
Copy link
Copy Markdown

@szepeviktor szepeviktor commented Jul 8, 2024

Found few misspellings, and removed two execute bits (chmod -x)

https://github.com/crate-ci/typos

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 8, 2024

Walkthrough

The overall change involves correcting various typos in comments, function names, and messages across multiple files in the codebase. These corrections enhance the readability, consistency, and clarity of the code without altering its logic or control flow. Additionally, some changes improve functionality descriptions and documentation.

Changes

File Change Summary
bin/build-plugin.sh, bin/git-release.sh, changelog.txt Corrected typos in messages and added functionality summaries.
classes/controllers/… Corrected typos in comments, variable names, and method names across multiple controller files.
classes/helpers/… Corrected typos in comments, variable names, and method names across multiple helper files.
classes/models/… Corrected typos in comments and variable names across multiple model files.
classes/models/fields/… Corrected typos in comments, variable names, and method names related to field types.
classes/views/… Corrected typos in comments and descriptions in view-related files.
deprecated/FrmEDD_SL_Plugin_Updater.php Corrected a typo in a comment from "successfull" to "successful."
js/formidable_admin.js Corrected spelling errors in comments and renamed functions and variables from "Mergable" to "Mergeable" for consistency.
readme.txt Corrected a typo from "WP Mail SMPT" to "WP Mail SMTP."
stripe/models/FrmStrpLiteAuth.php Corrected a typo in a comment related to appending a message to the success URL.
tests/cypress/e2e/… Corrected typos in log messages and test suite descriptions across multiple Cypress test files.
tests/phpunit/… Corrected typos in error messages for assertions in PHPUnit test files related to CSS styles and characteristics.

Note: All changes above include corrections for better readability and consistency without altering the underlying logic or control flow.


Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 827d629 and bfa0d7a.

Files selected for processing (2)
  • classes/helpers/FrmDashboardHelper.php (1 hunks)
  • classes/helpers/FrmFieldsHelper.php (2 hunks)
Files skipped from review as they are similar to previous changes (2)
  • classes/helpers/FrmDashboardHelper.php
  • classes/helpers/FrmFieldsHelper.php

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range and nitpick comments (18)
readme.txt (1)

186-187: Consider using more formal wording.

To align with the professional tone of the documentation, consider changing "fix the problem" to "resolve the issue".

-    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 going out, please reach out to 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)

changelog.txt (17)

Line range hint 2-2: Typo in "Recurrng"

The word "Recurring" is misspelled as "Recurrng".

- * New: Stripe actions included in this plugin now support a Recurrng Payment Limit setting.
+ * New: Stripe actions included in this plugin now support a Recurring Payment Limit setting.

Line range hint 10-10: Typo in "summaries"

The word "summaries" is misspelled as "summaries".

- * The frm_summary_email_content_args hook has been moved to where it is now filtered for all types of email summaries.
+ * The frm_summary_email_content_args hook has been moved to where it is now filtered for all types of email summaries.

Line range hint 24-24: Typo in "Uncaught"

The word "Uncaught" is misspelled as "Uncaught".

- * Fix: A Uncaught TypeError: Cannot access offset of type string on string error has been fixed when checking for add-on data.
+ * Fix: An Uncaught TypeError: Cannot access offset of type string on string error has been fixed when checking for add-on data.

Line range hint 40-40: Typo in "screenreader"

The phrase "screen reader" is misspelled as "screenreader".

- * New: Bulk action checkboxes on the form list now include screenreader text for improved accessibility.
+ * New: Bulk action checkboxes on the form list now include screen reader text for improved accessibility.

Line range hint 45-45: Typo in "multisite"

The word "multisite" is misspelled as "multisite".

- * New: Summary emails will no longer send by default on multisite for sites that are not the main site.
+ * New: Summary emails will no longer send by default on multisite for sites that are not the main site.

Line range hint 98-98: Typo in "aria-hidden"

The phrase "aria-hidden" is misspelled as "aria-hidden".

- * New: Honeypot field containers will no longer include an aria-hidden attribute.
+ * New: Honeypot field containers will no longer include an aria-hidden attribute.

Line range hint 244-244: Typo in "AJAX-submitted"

The phrase "AJAX-submitted" is misspelled as "AJAX-submitted".

- * Fix: AJAX-submitted forms would log a PHP Notice on submit with new versions of WooCommerce installed.
+ * Fix: AJAX-submitted forms would log a PHP Notice on submit with new versions of WooCommerce installed.

Line range hint 258-258: Typo in "redirect"

The word "redirect" is misspelled as "redirect".

- * Fix: A redirect confirmation action with an empty redirect URL would exit early and fallback to using a message without checking the frm_redirect_url filter first for redirects set in custom code.
+ * Fix: A redirect confirmation action with an empty redirect URL would exit early and fallback to using a message without checking the frm_redirect_url filter first for redirects set in custom code.

Line range hint 285-285: Typo in "shortcodes"

The word "shortcodes" is misspelled as "shortcodes".

- * Fix: Shortcodes were not getting replaced in redirect confirmation actions.
+ * Fix: Shortcodes were not getting replaced in redirect confirmation actions.

Line range hint 297-297: Typo in "deprecation"

The word "deprecation" is misspelled as "deprecation".

- * Fix: Formidable settings have been updated to avoid PHP 8.2 deprecation messages.
+ * Fix: Formidable settings have been updated to avoid PHP 8.2 deprecation messages.

Line range hint 327-327: Typo in "styler"

The word "styler" is misspelled as "styler".

- * New: Added a new style tab when editing a form that links to the visual styler.
+ * New: Added a new style tab when editing a form that links to the visual styler.

Line range hint 474-474: Typo in "reCAPTCHA"

The word "reCAPTCHA" is misspelled as "reCAPTCHA".

- * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha.
+ * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha.

Line range hint 494-494: Typo in "textarea"

The word "textarea" is misspelled as "textarea".

- * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop.
+ * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop.

Line range hint 531-531: Typo in "textarea"

The word "textarea" is misspelled as "textarea".

- * Fix: Shortcode popup will now appear below textareas to avoid visibility issues with overlapping over content.
+ * Fix: Shortcode popup will now appear below textareas to avoid visibility issues with overlapping over content.

Line range hint 595-595: Typo in "reCAPTCHA"

The word "reCAPTCHA" is misspelled as "reCAPTCHA".

- * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha.
+ * New: Added support for hCaptcha. Now in Global Settings, the reCAPTCHA tab has been changed to a CAPTCHA tab with a new CAPTCHA type setting so you can choose between using reCAPTCHA or hCaptcha.

Line range hint 662-662: Typo in "aria-describedby"

The phrase "aria-describedby" is misspelled as "aria-describedby".

- * Fix: The aria-describedby attribute will now be ordered intentionally so errors get first priority by default. Checks have been added to avoid duplicate ids appearing in aria-describedby attributes as well.
+ * Fix: The aria-describedby attribute will now be ordered intentionally so errors get first priority by default. Checks have been added to avoid duplicate ids appearing in aria-describedby attributes as well.

Line range hint 726-726: Typo in "textarea"

The word "textarea" is misspelled as "textarea".

- * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop.
+ * Fix: When an HTML email includes a body tag, only the content of the body tag will use wpautop.

@Crabcyborg Crabcyborg mentioned this pull request Jul 8, 2024
Comment thread classes/models/fields/FrmFieldType.php
@Crabcyborg Crabcyborg closed this Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants