-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Story Poster: Use dimensions array instead of size name #12418
Conversation
Plugin builds for a1b6616 are ready 🛎️!
|
Size Change: 0 B Total Size: 2.72 MB ℹ️ View Unchanged
|
Does it work? As discussed, would be nice to have some sorts of tests verifying that this actually solves the reported bug. With this approach here it should be doable to that with PHP tests alone, no E2E tests needed (though that would be the last resort). Alternatively, if we can't have tests, at the very least we should add comments explaining why we do it that way. |
@swissspidy Unit tests added. Closing other PR in favour of this. |
tests/phpunit/integration/tests/REST_API/Stories_Controller.php
Outdated
Show resolved
Hide resolved
tests/phpunit/integration/tests/REST_API/Stories_Controller.php
Outdated
Show resolved
Hide resolved
tests/phpunit/integration/tests/REST_API/Stories_Controller.php
Outdated
Show resolved
Hide resolved
The tests don't work, as in, they demonstrate the bugfix. If I undo the changes to Note that for the QA instructions you can reuse the reproduction steps from the issue. |
The fix does work, I just used the wrong test data. I have updated the fixture data and tests pass and you can see them pass. |
When I undo the changes to |
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of adjustments needed, as per my recent comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This still needs to be addressed AFAICT. After that this should be ready. |
I believe I fixed these issues with new test data. |
Just verified that it's still an issue. 3be82da was the only change since I flagged this. |
Excellent! 🎉 |
Reproduced this problem (thanks to @LuckynaSan and @spacedmonkey for your help) by following these steps:
Verified the fix by loading the |
Context
Summary
Another solution to #12354. If you pass an array of dimensions instead of passing size name it bypasses the content width check. See
Relevant Technical Choices
To-do
User-facing changes
Testing Instructions
This PR can be tested by following these steps:
Reviews
Does this PR have a security-related impact?
Does this PR change what data or activity we track or use?
Does this PR have a legal-related impact?
Checklist
Type: XYZ
label to the PRFixes #12354