Skip to content

Update readme for v6.11#1810

Merged
Crabcyborg merged 2 commits into
masterfrom
update_readme_6.11
Jun 19, 2024
Merged

Update readme for v6.11#1810
Crabcyborg merged 2 commits into
masterfrom
update_readme_6.11

Conversation

@Crabcyborg
Copy link
Copy Markdown
Contributor

No description provided.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 17, 2024

Walkthrough

The update from version 6.10 to 6.11 of the "Formidable Forms - Contact Form, Survey & Quiz Form Builder for WordPress" plugin introduces new functionalities and optimizations. Key enhancements include improved field error handling, automatic layout class conflict resolution, and reduced load times for the form builder. Style consistency and support for a new Stripe action setting (Recurring Payment Limit) are also added. Additionally, various fixes and removal of obsolete files contribute to improved performance and reduced plugin size.

Changes

Files/Groups Change Summary
changelog.txt Summarizes all the new features, optimizations, and fixes in version 6.11.
readme.txt Updated to reflect the changes in version 6.11, including new feature descriptions and declared updates.
...bootstrap.js, ...popper.js Removed references to JavaScript map files to streamline loading.
...form-preview.php, ...filters.php Fixed issues such as conflicting title tags in the form preview HTML and PHP warnings for field removal.
...errors.js, ...layout.js Enhanced JavaScript validation to use field keys and added logic to automatically resolve layout conflicts.
...styles.css, ...fonts/*.ttf Updated field placeholder font sizes and removed old CSS styles and unnecessary font files.
...api-actions.php Improved support for sending data in repeated API actions.

Sequence Diagram(s)

Improved Field Error Handling

sequenceDiagram
    participant User
    participant Form
    participant JavaScript
    User->>Form: Submits form
    Form-->>JavaScript: Send field data
    JavaScript->>JavaScript: Validate using field keys
    JavaScript-->>Form: Field error feedback
    Form-->>User: Display errors inline
Loading

Layout Class Conflict Resolution

sequenceDiagram
    participant User
    participant FormBuilder
    participant LayoutJS
    User->>FormBuilder: Selects layout class
    FormBuilder-->>LayoutJS: Send layout choice
    LayoutJS->>LayoutJS: Remove conflicting classes
    LayoutJS-->>FormBuilder: Apply new layout class
Loading

Stripe Recurring Payment Limit Setting

sequenceDiagram
    participant User
    participant StripeSettings
    participant PaymentProcessor
    User->>StripeSettings: Configure Recurring Payment Limit
    StripeSettings-->>PaymentProcessor: Send limit setting
    PaymentProcessor->>PaymentProcessor: Enforce limit on transactions
    PaymentProcessor-->>User: Confirmation or error
Loading

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3edeff1 and 8172f14.

Files selected for processing (1)
  • readme.txt (3 hunks)
Additional context used
LanguageTool
readme.txt

[misspelling] ~28-~28: This word is normally spelled as one. (EN_COMPOUNDS_MULTI_PAGE)
Context: ...ptions like an email subscription form, multi-page form, file upload form, quiz grading, o...


[style] ~28-~28: For a more polite and respectful tone, consider rephrasing with ‘please’. (DONT_FORGET)
Context: ...onships, and cascading dropdown fields. Don't forget the calculated fields, front-end form e...


[misspelling] ~88-~88: This word is normally spelled as one. (EN_COMPOUNDS_MULTI_PAGE)
Context: ...idable's rich array of features include multi-page forms, save-and-continue options, casca...


[style] ~105-~105: Consider using a more formal and expressive alternative to ‘awesome’. (AWESOME)
Context: ...Form Solution == > Formidable Forms is an awesome professional form builder. There is muc...


[uncategorized] ~105-~105: Did you mean “too”? (WAY_TOO)
Context: ...rofessional form builder. There is much to like about Formidable Forms. From the d...


[misspelling] ~113-~113: This word is normally spelled as one. (EN_COMPOUNDS_MULTI_STEP)
Context: ...i-Step Forms**: Boost conversions with [multi-step forms](https://formidableforms.com/feat...


[grammar] ~182-~182: The verb “Double-check” is spelled with a hyphen. (DOUBLE_HYPHEN)
Context: ...emails, try the following steps: 1. Double check the email address in your Email action ...


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


[style] ~264-~264: Try using a synonym here to strengthen your writing. (GIVE_PROVIDE)
Context: ...tm_campaign=liteversion). A Pro license gives you access to the full version of Formidabl...


[style] ~289-~289: The expression “come in handy” is rather colloquial. Consider replacing it to add a more formal tone to your writing. (COME_IN_HANDY)
Context: ...f our advanced premium fields that will come in handy: * File Upload * Rich Text * Date * Ti...


[uncategorized] ~302-~302: It seems likely that a singular genitive (’s) apostrophe is missing. (AI_HYDRA_LEO_APOSTROPHE_S_XS)
Context: ...ple kids, job history, and much more. * Tags * Summary - Great to review responses b...


[uncategorized] ~345-~345: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...your website with over 5,000+ marketing apps including: * SendInBlue * Zoho CRM * Z...


[style] ~388-~388: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative. (A_LOT_OF)
Context: ...e load speed improvement for forms with a lot of fields. * New: XML import has been upda...


[grammar] ~390-~390: Using ‘plenty’ without ‘of’ is considered to be informal. (PLENTY_OF_NOUNS)
Context: ...cimal separator would have an incorrect amount value when the amount value had a single deci...


[grammar] ~390-~390: Using ‘plenty’ without ‘of’ is considered to be informal. (PLENTY_OF_NOUNS)
Context: ...have an incorrect amount value when the amount value had a single decimal point like 11,5. *...


[style] ~400-~400: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...ings is now stored in memory and reused in order to significantly improve performance in th...


[style] ~400-~400: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative. (A_LOT_OF)
Context: ...ance in the form builder for forms with a lot of fields. * Fix: Rootline and progress ba...


[style] ~403-~403: ‘by mistake’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_BY_MISTAKE)
Context: ...ix: Submit button fields were appearing by mistake in WooCommerce products. * The parser f...


[uncategorized] ~409-~409: When ‘set-up’ is used as a noun or modifier, it needs to be hyphenated. (VERB_NOUN_CONFUSION)
Context: ... been added to help improve the initial set up process. * New: Submit buttons can now ...


[uncategorized] ~413-~413: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... has been updated for calculation field options so field IDs are now still visible for ...


[style] ~416-~416: Consider using a different verb for a more formal wording. (FIX_RESOLVE)
Context: ...leted now after an action is deleted to fix an issue with old floating tooltips. [...

Additional comments not posted (3)
readme.txt (3)

6-6: Update to Tested up to: 6.5.4 reflects the latest WordPress version compatibility.


8-8: Updated Stable tag: 6.11 aligns with the new plugin version, ensuring users download the latest version.


374-385: The changelog entries from lines 374 to 385 effectively summarize the new features and fixes introduced in version 6.11. These entries are clear and provide a good level of detail about the changes, which include enhancements to field error handling, layout class management, performance optimizations, and Stripe integration, as well as several important bug fixes.


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 (3)
changelog.txt (3)

5-5: This entry succinctly communicates performance enhancements. However, it might be beneficial to specify what kind of optimizations were made if possible.


11-11: This fix is somewhat vague. It might be helpful to specify what was updated to support repeated API actions better.


12-12: This line succinctly states the removal but does not specify which styles were removed. While not critical, more detail could be useful for clarity.

@Crabcyborg Crabcyborg merged commit f916040 into master Jun 19, 2024
@Crabcyborg Crabcyborg deleted the update_readme_6.11 branch June 19, 2024 13:40
@coderabbitai coderabbitai Bot mentioned this pull request Oct 1, 2024
This was referenced Nov 13, 2024
@coderabbitai coderabbitai Bot mentioned this pull request Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant