Add more change log items

[Crabcyborg]

These never got merged.

[coderabbitai]

Walkthrough

The pull request updates the changelog and readme documentation for version 6.18. It includes fixes for style settings such as ensuring float values retain their decimal places and handling invalid (undefined/NaN) values. Additional user interface corrections are made by adding a red outline for invalid checkbox fields, ensuring CSS classes are properly applied to form containers, and correcting the automatic width for dropdown fields. In addition, a deprecated file is removed and a setting for excluding Formidable in the admin bar is relocated to miscellaneous settings.

Changes

Files	Change Summary
changelog.txt, readme.txt	Updated style settings fixes: float values now retain decimals; handling of invalid (undefined/NaN) values; red outline added for invalid checkboxes; CSS classes correctly applied; dropdown width adjusted.
changelog.txt	Removed deprecated file (.../stripe/views/payments/entry_sidebar.php) and relocated the setting for excluding Formidable from the admin bar to miscellaneous settings.

Possibly related PRs

• Prepare for v6.16.1.2 #2105: Addresses fixes for float value handling and styling issues similar to those implemented here.
• Update readme 6.15 #2016: Implements corrections to preserve float decimal places and handle invalid style values.
• Update readme for v6.18 #2242: Modifies style settings validations and CSS class applications in a similar context.

---

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

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

readme.txt (1)

378-379: LGTM! Consider enhancing the second fix description.

The changelog entries accurately document the bug fixes for style settings. The first entry is clear and specific.

Consider making the second entry more specific by mentioning which style settings were affected:

-* Fix: Some style setting values would result in invalid undefined or NaN values.
+* Fix: Style setting values for [specific settings] would result in undefined or NaN values.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3e2f106 and 9924f03.

📒 Files selected for processing (2)

• changelog.txt (1 hunks)
• readme.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: PHP 8 tests in WP trunk
• GitHub Check: PHP 8 tests in WP trunk
• GitHub Check: PHP 7.4 tests in WP trunk
• GitHub Check: Cypress
• GitHub Check: Cypress
• GitHub Check: PHP 7.4 tests in WP trunk

🔇 Additional comments (1)

changelog.txt (1)

3-3: Improved form validation UX with visual feedback

The addition of red outline for invalid checkbox fields improves form usability by providing clear visual feedback to users when validation fails.