Playwright: Pass the payload to createPost in data instead of query params to avoid URI too long errors. #59463
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.
What?
This adjusts the playwright request utility to pass post params as data instead of as query params in the uri.
Why?
Because the post params are currently sent in query params, if you wanted to create a large post via this API you will encounter URI too long errors. I ran into this problem in #59427
How?
By passing the post attributes in the
data
attribute instead it will not cause URI too long errors no matter how long the post is that you want to create via the API.Testing Instructions
I believe that seeing the Playwright e2e tests pass in CI will be sufficient to prove that this still works as it should.
Testing Instructions for Keyboard
n/a
Screenshots or screencast
n/a