Repository navigation
Replace assertEquals with assertSame for stricter checks - #11707
shreyasikhar wants to merge 2 commits into
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. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
Compare REST response status codes and theme-preview hook priorities with integer expectations. Check ability pagination headers against string expectations without casting the returned values. Developed in: #11707 Props shreyasikhar26. See #64895. git-svn-id: https://develop.svn.wordpress.org/trunk@63935 602fd350-edb4-49c9-b593-d223f7449a82
Compare REST response status codes and theme-preview hook priorities with integer expectations. Check ability pagination headers against string expectations without casting the returned values. Developed in: WordPress/wordpress-develop#11707 Props shreyasikhar26. See #64895. Built from https://develop.svn.wordpress.org/trunk@63935 git-svn-id: http://core.svn.wordpress.org/trunk@63101 1a063a9b-81f0-0310-95a4-ce76da25c4cd
|
PR #11707 landed with https://core.trac.wordpress.org/changeset/63935 |
Replace loose assertions with strict comparisons for REST response status codes, ability pagination headers, and theme-preview hook priorities.
The pagination assertions compare string expectations with the original response headers, preserving checks of both value and type. The bulk-edit assertion is already covered by r63934 and is no longer part of this diff.
Trac ticket: https://core.trac.wordpress.org/ticket/64895
Validation
Use of AI Tools
AI assistance: Yes.
Tools: GitHub Copilot for the original conversions; OpenAI Codex (GPT-6) for the trunk refresh, conflict resolution, header-type review, local validation, and description update. The changes remain subject to human review.