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

Revert "bug #20184 [FrameworkBundle] Convert null prefix to an empty string in translation:update (chalasr)"#20433

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

Merged
fabpot merged 1 commit intosymfony:2.7fromchalasr:framework/revert-3f650f8
Nov 7, 2016

Conversation

@chalasr
Copy link
Member

QA
Branch?2.7
Bug fix?no
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets#20184 (comment)
LicenseMIT
Doc PRn/a

This reverts commit3f650f8 because the fix is not valid.
It is actually not possible to have an option with value optional given empty to beempty if this one has a default value. The default value will always be the one returned, see#20184 (comment) for details.

… empty string in translation:update (chalasr)"This reverts commit3f650f8, reversingchanges made to962248d.
@chalasrchalasr changed the titleRevert "bug #20184 [FrameworkBundle] Convert null prefix to an empty string in translation:update (chalaRevert "bug #20184 [FrameworkBundle] Convert null prefix to an empty string in translation:update (chalasr)"Nov 7, 2016
@javiereguiluz
Copy link
Member

👍

Status: reviewed

@stof
Copy link
Member

stof commentedNov 7, 2016

👍

@stof
Copy link
Member

stof commentedNov 7, 2016

@javiereguiluz why adding the 3.2 milestone ? This targets the 2.7 branch, as this is where the buggy patch was merged

@javiereguiluz
Copy link
Member

javiereguiluz commentedNov 7, 2016
edited
Loading

@stof you are right. The idea of the "3.2" milestone is"PRs to be merged before the release of Symfony 3.2" and not"PRs to be merged exclusively for Symfony 3.2". It'd be sad to release 3.2.0 with well-known bugs that already have a solution and had to wait for 3.2.1.

@fabpot
Copy link
Member

Thank you@chalasr.

@fabpotfabpot merged commitb2fa7c4 intosymfony:2.7Nov 7, 2016
fabpot added a commit that referenced this pull requestNov 7, 2016
… to an empty string in translation:update (chalasr)" (chalasr)This PR was merged into the 2.7 branch.Discussion----------Revert "bug#20184 [FrameworkBundle] Convert null prefix to an empty string in translation:update (chalasr)"| Q             | A| ------------- | ---| Branch?       | 2.7| Bug fix?      | no| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#20184 (comment)| License       | MIT| Doc PR        | n/aThis reverts commit3f650f8 because the fix is not valid.It is actually not possible to have an option with value optional given empty to be `empty` if this one has a default value. The default value will always be the one returned, see#20184 (comment) for details.Commits-------b2fa7c4 Revert "bug#20184 [FrameworkBundle] Convert null prefix to an empty string in translation:update (chalasr)"
@chalasrchalasr deleted the framework/revert-3f650f8 branchNovember 7, 2016 15:27
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.2

Development

Successfully merging this pull request may close these issues.

5 participants

@chalasr@javiereguiluz@stof@fabpot@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp