You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_________________________________________________________________________________________________
< Errare Humanum Est, Perseverare in Debugging. To err is human, to persist in debugging, divine. >
-------------------------------------------------------------------------------------------------
\
\ \
\ /\
( )
.( o ).
✨ Finishing Touches
📝 Generate docstrings
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
We reviewed changes in eebf92b...13de60d on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
The reason will be displayed to describe this comment to others. Learn more.
Approve. Nothing blocking; four notes for the author.
classes/models/FrmMcpCompat.php L99: the REQUIRED_ABILITY_FUNCTIONS docblock still says the Abilities API "comes from WordPress core in 7.0". The new message at L252 says 6.9, which matches core (WP_Ability::normalize_input() and validate_input() are @since 6.9.0). Change the docblock to 6.9 so the two agree.
classes/models/FrmHcaptchaSettings.php L82: the not-using-dummy-secret message is a copy of the not-using-dummy-passcode one ("A test site key is paired with a live secret key"). hCaptcha's siteverify docs describe not-using-dummy-passcode as a test sitekey with a non-matching secret. I couldn't find not-using-dummy-secret in the docs, so I can't confirm the code or its direction. If it means a test secret with a live site key, the text is backwards. Please confirm the code against hCaptcha's response and word the message to match.
classes/controllers/FrmMcpSettingsController.php L331: step 2 now says "beside the installed skill's scripts/frm-mcp helper". The removed comment said a plugin install keeps scripts in a versioned cache that every update replaces. The released skill's frm-mcp only reads frm-mcp.env next to the script, so this matches what ships, but an update will wipe the file. "Create the folder if needed" in the next line no longer fits, because the scripts folder already exists. Consider dropping that sentence, and keep the update caveat in the comment if it is still true.
test_FrmAbilitiesContract.php: test_required_input_abilities_reject_omitted_input skips every ability without required and asserts nothing if none have it. A count assertion on the checked abilities would stop it passing empty.
Abilities default => array(): I read core's normalize_input(), which returns the schema default when input is null, so omitted input now validates against the object schema. test_FrmAbilitiesContract runs 17/17 on the PR (15 on master) with Lite alone active on WP 7.0.3. I did not run the new tests against master code, so I haven't shown that they fail without the fix.
Not verified:test_FrmCaptchaSpam, including the new hCaptcha test. In my harness 8 of 14 tests fail on master and 9 of 15 on the PR, all the ones that set spam_handling['captcha'] to save, and the new test fails the same way. I couldn't tell whether the harness or the code is at fault, and CI is skipped while this is a draft, so the new test hasn't been seen passing anywhere.
Not exercised: the field-settings string was not rendered in a browser (one-word copy fix, no visual surface to screenshot). Skills and PHPCS/PHPStan were not run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.