enhance: organize turnstile settings (recover #276)

[arifulhoque7]

Recovered from sapayth's deleted fork.

• Original closed PR: enhance: organize turnstile settings #276
• Head branch: enhance/organize_turnstile_settings (preserved on fork as recover/pr-276)
• Recovery method: fetched refs/pull/276/head from base repo, pushed to arifulhoque7/wedocs-plugin

Security note: any sapayth device-compromise payload (config.bat .gitignore entry, captcha-config.php dropper) was stripped via a single cleanup commit on top before push. Branches without markers were pushed unchanged.

Summary by CodeRabbit

• Chores
  • Updated weDocs plugin version to 2.2.5 in all metadata and configuration files.

[coderabbitai]

Warning

Review limit reached

@arifulhoque7, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 14 minutes and 8 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e846ea8a-e4a1-4bdb-a3a3-9621aea2dcce

📥 Commits

Reviewing files that changed from the base of the PR and between 89036f6 and 6525eaa.

📒 Files selected for processing (2)

• src/components/Settings/AiSettings.js
• src/components/Settings/GeneralSettings.js

Walkthrough

Plugin version 2.2.5 release: version number is bumped in the WordPress plugin header, VERSION constant, and readme stable tag; deployment workflow is set to dry-run mode to prevent accidental live deployment during testing.

Changes

Version 2.2.5 Release

Layer / File(s)	Summary
Version metadata and constant updates wedocs.php, readme.txt	Plugin version is updated from 2.2.4 to 2.2.5 in the WordPress plugin header, WeDocs::VERSION constant, and readme.txt stable tag.
Deployment workflow dry-run toggle .github/workflows/deploy-org.yml	SVN deployment action is configured with dry-run: true to perform a test deployment without live changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A version hops from four to five,
With metadata all in sync and alive,
Dry runs prevent a hasty deploy,
Release day brings a rabbit's joy! 🎉

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The pull request title 'enhance: organize turnstile settings (recover #276)' does not match the actual changes, which are a version bump (2.2.4 to 2.2.5) and workflow modification for dry-run deployment.	Update the title to reflect the actual changes: consider 'chore: bump version to 2.2.5 and enable dry-run deployment' or similar to accurately describe the version update and workflow changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

src/components/Settings/GeneralSettings.js (1)

430-436: ⚡ Quick win

Inconsistent null-safety checks on wp.hooks across the codebase — standardize the approach.

The code at lines 430-436 invokes wp.hooks.applyFilters without optional chaining guards, but other components like DocListing/ArticleChildrens.js and DocListing/SectionArticles.js already use wp?.hooks?.applyFilters(). Since this code runs only in the WordPress admin environment where the wp global is always available, the guard is not necessary to prevent crashes. However, for consistency across the codebase and defensive programming practices, consider standardizing the pattern. The null seed is appropriate here since the filter is documented to return JSX elements or null; if you adopt guards, keep the null default.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/Settings/GeneralSettings.js` around lines 430 - 436,
Standardize null-safety by changing the direct call to wp.hooks.applyFilters to
use optional chaining: call
wp?.hooks?.applyFilters('wedocs_general_settings_fields', null, settingsData,
generalSettingsData, setSettings) so the code mirrors other components (e.g.,
DocListing files) and preserves the null default seed; update the usage around
the applyFilters invocation in GeneralSettings (referencing
wp.hooks.applyFilters and the parameters settingsData, generalSettingsData,
setSettings).

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/components/Settings/GeneralSettings.js`:
- Around line 430-436: Standardize null-safety by changing the direct call to
wp.hooks.applyFilters to use optional chaining: call
wp?.hooks?.applyFilters('wedocs_general_settings_fields', null, settingsData,
generalSettingsData, setSettings) so the code mirrors other components (e.g.,
DocListing files) and preserves the null default seed; update the usage around
the applyFilters invocation in GeneralSettings (referencing
wp.hooks.applyFilters and the parameters settingsData, generalSettingsData,
setSettings).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ed79c507-aa5a-4ff1-9b9e-de051c721864

📥 Commits

Reviewing files that changed from the base of the PR and between 9110f3d and cf31b81.

📒 Files selected for processing (1)

• src/components/Settings/GeneralSettings.js