Skip to content

Update readme for v6.21#2359

Merged
Crabcyborg merged 1 commit into
masterfrom
update_readme_6.21
May 12, 2025
Merged

Update readme for v6.21#2359
Crabcyborg merged 1 commit into
masterfrom
update_readme_6.21

Conversation

@Crabcyborg
Copy link
Copy Markdown
Contributor

No description provided.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 12, 2025

Walkthrough

The changelog and readme files were updated for version 6.21, documenting enhancements and fixes related to spam prevention, Stripe payment field styling, and form builder usability. Updates include new spam validation features, improved honeypot field handling, expanded denylist validation, Stripe field style options, and various bug fixes. Metadata and compatibility information were also updated.

Changes

File(s) Change Summary
changelog.txt Added version 6.21 changelog entries detailing new features (spam prevention enhancements, Stripe styling improvements, form builder usability updates), bug fixes, and implementation notes. No changes were made to previous version notes except for the addition of 6.21.
readme.txt Updated plugin metadata for WordPress 6.8.1 compatibility and new stable tag 6.21. Added 6.21 changelog details, removed 6.18 changelog entries, and incremented version numbers. No changes to exported or public entity declarations.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant FormBuilder
    participant SpamValidator
    participant StripeField
    participant WordPressSpamDB

    User->>FormBuilder: Submit form
    FormBuilder->>SpamValidator: Validate with honeypot, stopforumspam, denylist
    SpamValidator->>WordPressSpamDB: Compare against spam comments (if enabled)
    SpamValidator-->>FormBuilder: Return spam check result
    alt Stripe payment field present
        FormBuilder->>StripeField: Apply style updates and layout
    end
    FormBuilder-->>User: Show submission result or error
Loading

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


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.

❤️ 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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.

Support

Need 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)

  • @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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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

🧹 Nitpick comments (5)
readme.txt (1)

375-392: Changelog entry grammar and clarity improvements.

A few minor refinements could improve readability and consistency:

  • Line 385: Simplify the phrasing to avoid redundant verbs.
    - * New: A new layout setting has been added to Stripe settings that adds support for the accordion layout.
    + * New: Stripe settings now include a layout option for the accordion style.
  • Line 388: Wrap the error message in quotes for clarity.
    - * Fix: A Cannot set properties of null JavaScript error when duplicating a field has been fixed.
    + * Fix: A "Cannot set properties of null" JavaScript error when duplicating a field has been fixed.
  • Ensure all bullet points start with New: or Fix: and use consistent tense.

These refinements will polish the changelog before publication.

🧰 Tools
🪛 LanguageTool

[grammar] ~385-~385: Possible subject-verb agreement error detected.
Context: ... has been added to Stripe settings that adds support for the accordion layout. * Fix...

(PLURAL_THAT_AGREEMENT)


[grammar] ~388-~388: Did you mean “I”?
Context: ...hecking for spam has been fixed. * Fix: A Cannot set properties of null JavaScrip...

(A_MD_VB)

changelog.txt (4)

2-2: Verify version header formatting consistency
Ensure that the new version header = 6.21 = matches the spacing and underline style of previous versions (e.g., = 6.20 =) for consistency across the changelog.


3-3: Clarify honeypot setting relocation
The move of honeypot settings to the global Captcha/Spam section is clear; consider adding a brief note or link to the updated UI location in the documentation for user guidance.


4-4: Validate stopforumspam API integration details
This bullet introduces the stopforumspam API check—ensure that developer docs or settings pages include guidance on obtaining and configuring API keys, as well as rate-limit considerations.


18-18: Inconsistent bullet prefix
The final entry lacks a category tag (* New: or * Fix:) before the description. Please add the appropriate prefix for consistency with the rest of the changelog.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 419c7fe and 2188cba.

📒 Files selected for processing (2)
  • changelog.txt (1 hunks)
  • readme.txt (2 hunks)
🧰 Additional context used
🪛 LanguageTool
readme.txt

[grammar] ~385-~385: Possible subject-verb agreement error detected.
Context: ... has been added to Stripe settings that adds support for the accordion layout. * Fix...

(PLURAL_THAT_AGREEMENT)


[grammar] ~388-~388: Did you mean “I”?
Context: ...hecking for spam has been fixed. * Fix: A Cannot set properties of null JavaScrip...

(A_MD_VB)

⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: Cypress
  • GitHub Check: PHP 7.4 tests in WP trunk
  • GitHub Check: PHP 8 tests in WP trunk
  • GitHub Check: Cypress
  • GitHub Check: PHP 7.4 tests in WP trunk
  • GitHub Check: PHP 8 tests in WP trunk
🔇 Additional comments (15)
readme.txt (2)

6-6: Confirm the "Tested up to" version matches plugin compatibility.

The Tested up to: 6.8.1 header has been updated; please verify that this reflects the latest supported WordPress version and that compatibility testing has been completed accordingly.


8-8: Stable tag bump is correct for v6.21.

The Stable tag: 6.21 line aligns with the intended release version.

changelog.txt (13)

5-5: Approve comprehensive denylist validation
The new denylist comparison and custom word settings are well described and provide flexible spam blocking.


6-6: Approve WordPress spam comments comparison
Adding a global setting to compare entries against WordPress spam comments is accurately documented and consistent with the other spam-prevention features.


7-7: Approve default option validation change
Noting that option values are now validated by default, along with the provided filter to revert, is clear and actionable.


8-8: Approve Stripe border radius styling update
The description of the new border radius support for Stripe payment fields aligns with the broader styling enhancements.


9-9: Approve Stripe label padding fix
Updating label padding to reflect style settings is clearly communicated and enhances consistency.


10-10: Approve Stripe input weight support
Bullet succinctly captures the new input weight style option for Stripe fields, matching behavior of other fields.


11-11: Approve Stripe font family support
Including font family style for Stripe fields brings them in line with other form elements; documentation is accurate.


12-12: Approve Stripe accordion layout option
The new accordion layout setting is well noted and expands the customization capabilities.


13-13: Approve paragraph placeholder fix
Fixing placeholder display in paragraph fields on the builder page is clearly documented and indicates improved UX.


14-14: Approve fatal error fix on submit
Describes the resolution of a submit-time fatal error due to unexpected spam data; documentation is precise.


15-15: Approve JavaScript null-property error fix
The fix for the “Cannot set properties of null” error when duplicating a field is clearly stated.


16-16: Approve numeric sorting fix
Corrects the sorting of number fields as numbers rather than strings; the entry is concise and correct.


17-17: Approve Stripe style-settings bug fix
Addresses cases where Stripe fields used wrong style settings; the bullet is clear and accurate.

@Crabcyborg Crabcyborg merged commit 21a644e into master May 12, 2025
34 checks passed
@Crabcyborg Crabcyborg deleted the update_readme_6.21 branch May 12, 2025 12:04
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