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

[2.8] [Form] Rename CollectionType options for entries#15025

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.8fromwouterj:issue_7831
Oct 11, 2015

Conversation

wouterj
Copy link
Member

Description

Replaces#13820 for the 2.8 branch.

Original description:

type andoptions are extremely generic. Prefixing them withentry_ makes it clear what they are configuring.

About the property deprecation it is the same story as#13717 and I don't know which direction you want me to go.

I've tried to apply the comments in the previous PR, but got a bit lost in the normalizers/default closure stuff. I hope I did everything correctly, but please review :)

PR Info Table

QA
Bug fix?no
New feature?yes
BC breaks?no
Deprecations?yes
Tests pass?yes
Fixed tickets#7831
LicenseMIT
Doc PRsymfony/symfony-docs#5051

@@ -52,12 +52,12 @@ class ResizeFormListener implements EventSubscriberInterface
*/
private $deleteEmpty;

public function __construct($type, array $options = array(), $allowAdd = false, $allowDelete = false, $deleteEmpty = false)
public function __construct($entryType, array $entryOptions = array(), $allowAdd = false, $allowDelete = false, $deleteEmpty = false)
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you revert the variable renames in this method? They don't really make sense now IMO.

@stof
Copy link
Member

We need a few legacy tests using the old option names

@fabpot
Copy link
Member

@wouterj We need to finish this one this week if we want to include it in 2.8.

@wouterj
Copy link
MemberAuthor

@fabpot I'm sorry for the delay. fixed all comments & added some legacy tests. Should be ready to merge now

@@ -791,7 +791,7 @@ public function testSubmitSingleExpandedRequiredEmptyNoChoices()
$this->assertTrue($form->isSynchronized());
}

public functiontestSubmitSingleExpandedRequiredFalse()
public functiontestSubmiCollectiontSingleExpandedRequiredFalse()
Copy link
Member

Choose a reason for hiding this comment

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

missingt ofSubmit

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

This change seems like a mistake, reverted it

@wouterj
Copy link
MemberAuthor

I cannot relate any of the build failures to changes in this PR

@fabpot
Copy link
Member

Thank you@wouterj.

@fabpotfabpot merged commit942a237 intosymfony:2.8Oct 11, 2015
fabpot added a commit that referenced this pull requestOct 11, 2015
… (WouterJ)This PR was merged into the 2.8 branch.Discussion----------[2.8] [Form] Rename CollectionType options for entriesDescription---Replaces#13820 for the 2.8 branch.Original description: > `type` and `options` are extremely generic. Prefixing them with `entry_` makes it clear what they are configuring. > About the property deprecation it is the same story as#13717 and I don't know which direction you want me to go.I've tried to apply the comments in the previous PR, but got a bit lost in the normalizers/default closure stuff. I hope I did everything correctly, but please review :)PR Info Table---| Q             | A| ------------- | ---| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | yes| Tests pass?   | yes| Fixed tickets |#7831| License       | MIT| Doc PR        |symfony/symfony-docs#5051Commits-------942a237 Rename CollectionType options for entries
@wouterjwouterj deleted the issue_7831 branchOctober 11, 2015 09:33
@craue
Copy link
Contributor

I'm usingtype and expected to see the deprecation notice, but it's not triggered (when running tests with the PHPUnit bridge enabled).

weaverryan added a commit to symfony/symfony-docs that referenced this pull requestOct 15, 2015
This PR was submitted for the 2.7 branch but it was merged into the 2.8 branch instead (closes#5051).Discussion----------Rename CollectionType entry options| Q | A| --- | ---| Doc fix? | no| New docs? | yes (symfony/symfony#15025)| Applies to | 2.7+| Fixed tickets | -Commits-------1b00278 Rename CollectionType entry options
craue added a commit to craue/CraueConfigBundle that referenced this pull requestOct 20, 2015
@fabpotfabpot mentioned this pull requestNov 16, 2015
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

6 participants
@wouterj@stof@fabpot@craue@webmozart@xabbuh

[8]ページ先頭

©2009-2025 Movatter.jp