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

[WIP] Bootstrapped Options Resolver Component#2353

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
weaverryan merged 4 commits intosymfony:2.1fromwouterj:document_optionresolver
Apr 9, 2013

Conversation

@wouterj
Copy link
Member

QA
Doc fix?yes
New docs?no
Applies to2.1+
Fixed tickets#2030

/cc @bschussek

Copy link
Member

Choose a reason for hiding this comment

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

This is wrong. It cannot be found anywhere in 2.0

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

fixed

weaverryan added a commit that referenced this pull requestApr 9, 2013
[WIP] Bootstrapped Options Resolver Component
@weaverryanweaverryan merged commitfd8f013 intosymfony:2.1Apr 9, 2013
weaverryan added a commit that referenced this pull requestApr 9, 2013
@weaverryan
Copy link
Member

Hi Wouter!

This is a great entry - I've merged it in with only minor changes at sha:b98619e (including removing theversionadded - only because we'll shortly make 2.1 the "oldest-supported" version).

I did have one question - which I'll post as a line comment.

Thanks!

Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure this last part (starting withThe closure that is passed...) is very clear. I think we need an example here to show what you can actually do and how this closure is used.

Copy link
MemberAuthor

Choose a reason for hiding this comment

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

I'll add it if you (or anyone) can give me a good example (I can't find a simple good 'somewhat real use-case' example for this one).

@wouterj
Copy link
MemberAuthor

@weaverryan thanks for merging!
I planned to do some final (english) checking and commit squashing (those are a bit vague now) this week, but I'm happy you had some time improving the english!

However, are we going to remove every.. versionadded:: 2.1 block from the documentation soon? Otherwise, I disagree removing it here

@webmozart
Copy link
Contributor

Thank you for this great documentation! In my opinion, the example should be changed though. Entities are a very bad usage example, because entities are data holders that can change at any time. The OptionsResolver though is meant for configuring classes whose configuration does not change anymore after construction.

A better example might be aMailer class for example.

@webmozart
Copy link
Contributor

And I'm completely aware that I gave this stupid example myself in the README file :P

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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@wouterj@weaverryan@webmozart@stof

[8]ページ先頭

©2009-2025 Movatter.jp