Repository navigation
feat: tell a second browser from a second tab with a per-room session hash - #815
Conversation
🛝 WordPress PlaygroundsBuilt from f9bf712
|
26e4142 to
a11bfb0
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #815 +/- ##
============================================
+ Coverage 97.08% 97.09% +0.01%
- Complexity 269 271 +2
============================================
Files 30 30
Lines 4354 4370 +16
============================================
+ Hits 4227 4243 +16
Misses 127 127
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
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. |
|
Great implementation Joe. Hashing the session token per room cleanly groups tabs into browsers without leaking replayable tokens across rooms. Two small suggestions:
|
dea09e8 to
182336b
Compare
|
Thanks, you caught the |
I went with the column, as the issue recommends, and only a row someone writes for themselves gets a session, so WP-CLI, cron, application passwords, reserved rows and rows written on another user's behalf store an empty string; I haven't tested a real second device, only sessions faked from cookies in PHPUnit.
Fixes #725
Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with the column, the REST and export fields, and the tests.