[HttpClient] More on testing, how to test request, example

[SirRFI]

PR focused on HTTP Client's testing. Specifically:

• Adds more to general description
• Adds subsection about testing request data (such as which method was used, what headers/body, etc.) + example
• Adds standalone PHPUnit-based example - demonstrates how to replace client for testing and how to do assertions

[AntonioCS]

Hey,
When is this getting merged? The example regarding sending raw json data via POST really helped me out,
This should be in the official docs page.

[pbowyer]

This is a great addition to the documentation! I'm proposing a few changes to make the description of why this is useful clearer; the rest is good.

[andrewmy]

Super useful addition, had to figure this stuff out myself, hope it gets merged soon 🙏 A few nitpicks on English, hope they're correct 😅

[SirRFI]

Thanks for suggestions - rebased the PR and applied them.

[javiereguiluz]

@SirRFI thanks a lot for this contribution. It's now merged.

For future contributions, please note that we prefer to not include full examples in Symfony Docs. We think those belong to blog posts and tutorials, whereas Symfony Docs should focus on showing each separate feature. Thanks!

[AntonioCS]

@javiereguiluz I'm sorry... but why? Why can't the docs have complete examples? Proper examples! More examples....
A lot of devs learn better and quicker with more extensive examples. From the simplest usage to the more complex, from the more common usage to the more unique. How does this not make sense?

English is not the fist language of many of the devs (myself included) so sometimes things get lost in translation, but I can read the code and have a better understanding of how to use whatever thing from symfony I'm using.

This merge is a perfect example, it was exactly what I was looking for, what I wanted to do but didn't know how and the docs didn't have any examples. It was @SirRFI that pointed me to the PR and saved the day.

Is this to force people to go to symfony casts and similar websites?

[javiereguiluz]

The reason is that full-length examples are much more complex to maintain. We don't have the resources to do that and sadly, we'll never have them.

We can't keep with Symfony code pace (there are still many undocumented Symfony features) so just thinking about doing more things is wishful thinking.

I guess you'll be disappointed, but I think it's better to be honest and explain the true reasons.

[wouterj]

Btw, feedback is always welcome. But you completely lost me when you started suggesting that a couple volunteers would make their work worse so that other services can be monetized.
I'm sorry, but I definitely hope that this isn't something you really think about the many volunteers and the handful paid contributors in the Symfony community...

[AntonioCS]

Why not just prefix the examples with the version? I understand that at the top you can select the version but something differs between minor versions just say: "This complex example is for version x.y.z".
I'll say it again, this more complex example, that was in PR for months, removed a lot of work from my task by providing something read to use for my issue.

But if you can't keep up with symfony code, maybe put more links to those tutorials you mentioned? That might mitigate some of the symfony code issues.