Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Rename allowSuccessfulResponse to correct allowCustomResponseCode#9336

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
hkdobrev wants to merge1 commit intosymfony:masterfromhkdobrev:custom-response-code-fix
Closed

Rename allowSuccessfulResponse to correct allowCustomResponseCode#9336

hkdobrev wants to merge1 commit intosymfony:masterfromhkdobrev:custom-response-code-fix

Conversation

@hkdobrev
Copy link
Contributor

Introduced in5f0becf

The functionality was introduced insymfony/symfony#19822.
The method got renamed during code review, but was not updated in the docs.
symfony/symfony#19822 (comment)

…CodeIntroduced in5f0becfThe functionality was introduced insymfony/symfony#19822.The method got renamed during code review, but was not updated in the docs.symfony/symfony#19822 (comment)
@hkdobrevhkdobrev changed the titleRename missing allowCustomResponseCode to correct allowCustomResponseCodeRename allowSuccessfulResponse to correct allowCustomResponseCodeFeb 25, 2018
fabpot added a commit to silexphp/Silex that referenced this pull requestFeb 26, 2018
…obrev)This PR was merged into the 2.3.x-dev branch.Discussion----------Allow setting custom status code on exception responseCloses#1450.Prior and related PRs and issues:-symfony/symfony#19822-symfony/symfony-docs@5f0becf-symfony/symfony-docs#9336Commits-------7103511 Allow setting custom status code on exception response
@javiereguiluzjaviereguiluz added this to the3.4 milestoneFeb 26, 2018
@javiereguiluz
Copy link
Member

@hkdobrev very nice catch! We've merged it on 3.4, the oldest maintained branch that contains the error. That's why GitHub shows it as closed instead of merged, but it's merged. And congrats on your first Symfony Docs contribution too!

hkdobrev reacted with hooray emoji

javiereguiluz added a commit that referenced this pull requestFeb 26, 2018
…onseCode (hkdobrev)This PR was submitted for the master branch but it was merged into the 3.4 branch instead (closes#9336).Discussion----------Rename allowSuccessfulResponse to correct allowCustomResponseCodeIntroduced in5f0becfThe functionality was introduced insymfony/symfony#19822.The method got renamed during code review, but was not updated in the docs.symfony/symfony#19822 (comment)Commits-------0cda0d5 Rename missing allowCustomResponseCode to correct allowCustomResponseCode
@hkdobrevhkdobrev deleted the custom-response-code-fix branchFebruary 26, 2018 09:09
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

3.4

Development

Successfully merging this pull request may close these issues.

3 participants

@hkdobrev@javiereguiluz@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp