Repository navigation
feat: return WP_Error with specific refusal codes when presence write fails - #792
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
🛝 WordPress PlaygroundsBuilt from fbb556e
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #792 +/- ##
============================================
+ Coverage 94.93% 94.94% +0.01%
Complexity 268 268
============================================
Files 30 30
Lines 4123 4137 +14
============================================
+ Hits 3914 3928 +14
Misses 209 209
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
2d9293d to
1058be7
Compare
|
0.17.0 shipped before this landed, so the two |
|
Done in fbb556e. |
josephfusco
left a comment
There was a problem hiding this comment.
This looks good to me, thanks for adding!
The REST controller and WP-CLI don't pass
wp_error, since they already answer recording off (501) and a missing table (503) before writing, so the argument is for callers outside the plugin such as an awareness backend, and with it off every existingfalsecheck behaves as before.Fixes #736
Use of AI Tools
AI assistance: Yes
Tool(s): Google Antigravity, Claude Code
Model(s): Gemini 3.8 Flash, Claude Opus 5.5
Used for: The first draft (Gemini); rebuilding it on #789's
$args, the tests and the README (Claude); reviewed and run locally by me.