v2.0.0

[jack-arturo]

• New React-based admin UI
• Added AffiliateWP integration: New Affiliate, Affiliate Status Updated, New Visit, Referral Earned)
• Added SearchWP integration: Search Performed, Search No Results
• Added PrettyLinks integration: Outbound Link Click
• Added ClickWhale integration: Outbound Link Click
• Added new WordPress core triggers: New Post Comment, New Comment Reply, Post Published, Post Updated, Post Status Changed
• Added trigger: Easy Digital Downloads - Discount Used
• Added trigger: WooCommerce - Coupon Used
• Fixed PHP warning when users logged in with an invalid username

Summary by CodeRabbit

• Documentation
  • Expanded the changelog for version 2.0.0 to include more details on AffiliateWP integration events.
  • Added new integrations for SearchWP, PrettyLinks, and ClickWhale with tracked events.
  • Documented new triggers for Easy Digital Downloads and WooCommerce.

[coderabbitai]

Walkthrough

The changelog in the readme.txt file was expanded for version 2.0.0, detailing specific events for AffiliateWP integration and adding new integrations and triggers for SearchWP, PrettyLinks, ClickWhale, Easy Digital Downloads, and WooCommerce. No code or public entity changes were made; all updates are documentation only.

Changes

Cohort / File(s)	Change Summary
Changelog Documentation readme.txt	Expanded changelog for v2.0.0 with detailed integration events and new triggers; documentation only

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hopped across the docs,
Expanding notes in changelog blocks.
New triggers, integrations, all in sight,
No code disturbed, all words were light.
With every line, the story grew—
Just readme tweaks, no code to review!
🐇✨

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/2.0.0

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate unit tests to generate unit tests for 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

readme.txt (2)

132-132: Fix stray closing parenthesis.

There's an unmatched ')' at the end of the line.

Apply this diff:

-* Added AffiliateWP integration: New Affiliate, Affiliate Status Updated, New Visit, Referral Earned)
+* Added AffiliateWP integration: New Affiliate, Affiliate Status Updated, New Visit, Referral Earned

---

134-134: Standardize plugin name: “Pretty Links” (with space).

The official branding is “Pretty Links”. Use consistent naming across the readme.

-* Added PrettyLinks integration: Outbound Link Click
+* Added Pretty Links integration: Outbound Link Click

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3d7903d and 13c239d.

📒 Files selected for processing (1)

• readme.txt (1 hunks)

🔇 Additional comments (2)

readme.txt (2)

132-135: Add new integrations to the “Supported Integrations” section for consistency.

Since you’ve added SearchWP, Pretty Links, and ClickWhale here, also list them under “Supported Integrations” above to keep the sections aligned.

---

137-138: Trigger/Event Names Verified – Documentation Matches Implementation

I’ve confirmed that the trigger labels in readme.txt exactly match the names emitted in code and shown in the admin UI:

• includes/integrations/edd/class-echodash-edd.php (lines 103 & 109): __('Discount Used', 'echodash')
• includes/integrations/woocommerce/class-echodash-woocommerce.php (lines 122 & 128): __('Coupon Used', 'echodash')

No doc-code drift detected.