Skip to content

Move HTTP client docs from components to guides #13916

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

Merged
merged 1 commit into from
Jun 30, 2020

Conversation

wouterj
Copy link
Member

@wouterj wouterj commented Jun 28, 2020

The component docs are actually very similar to the framework guide :). The biggest update is adding framework config examples to all examples showing global configuration and moving the framework integration section more to the start of the article.

We once added php-standalone and php-symfony tabs to the configuration blocks, which allow showing the same code for standalone and in-framework usage. This currently is used only in the Form component docs: https://symfony.com/doc/current/components/form.html#creating-a-simple-form I heavily used this in the article, so we can show both code examples in a concise matter.

Please let me know what you think! :)

@wouterj wouterj added this to the 4.4 milestone Jun 28, 2020
@wouterj wouterj changed the title Move HTTP client docs from a component to a guide Move HTTP client docs from components to guides Jun 28, 2020

Performance
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This diff is a bit messed-up: I moved the Performance (+ cURL support) a bit down. No contents where actually removed

Copy link
Member

@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

works for me, thanks!

@wouterj wouterj force-pushed the components/move-httpclient branch 3 times, most recently from 2e3566e to 029681f Compare June 28, 2020 13:30
@wouterj wouterj force-pushed the components/move-httpclient branch from 029681f to 9a51b28 Compare June 29, 2020 21:14
@wouterj
Copy link
Member Author

wouterj commented Jun 29, 2020

Thanks for your detailed review @javiereguiluz! I fully agree with you that the order was a bit messed-up. I did some reordering and better explanation about the configuration. Please have a look again :)

@wouterj wouterj force-pushed the components/move-httpclient branch from 9a51b28 to 242b4d0 Compare June 29, 2020 22:23
Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fantastic changes! Wouter, thanks a lot for this great contribution!!

I left a tiny comment, but I can do that change while merging.

@javiereguiluz javiereguiluz force-pushed the components/move-httpclient branch from 242b4d0 to 619e030 Compare June 30, 2020 08:05
@javiereguiluz
Copy link
Member

Merged! Thanks Wouter!

@javiereguiluz javiereguiluz merged commit 6efc1ab into symfony:4.4 Jun 30, 2020
@javiereguiluz
Copy link
Member

This is now merged up to master. There were some conflicts in 5.1. Please check if I reworded things right to mention AmpHttp support. Also, this paragraph needs review:

Support for HTTP/2 PUSH works out of the box when libcurl >= 7.61 is used with
PHP >= 7.2.17 / 7.3.4: pushed responses are put into a temporary cache and are
used when a subsequent request is triggered for the corresponding URLs.

Is this correct ... or does Amp also support HTTP/2 push? Always or only in certain versions? Thanks!

@wouterj wouterj deleted the components/move-httpclient branch June 30, 2020 08:34
@nicolas-grekas
Copy link
Member

Amp supports push yes, for all versions listed in the composer.json file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants