Skip to content

Added a note about the class option of the services defined via factories #5018

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 4 commits into from
Mar 14, 2015

Conversation

javiereguiluz
Copy link
Member

Q A
Doc fix? no
New docs? yes
Applies to 2.3+
Fixed tickets #4368

The original comment by @xabbuh in #4368 explained everything so well, that I decided to just copy it.

.. note::

When creating a service through a factory, the value chosen for the ``class``
option has no actual effect since the final class only depends on the object
Copy link
Member

Choose a reason for hiding this comment

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

"has no effect on the resulted service, since the actual class name only depends on the object returned by the factory."

Copy link
Member

Choose a reason for hiding this comment

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

"on the resulting service"?

@@ -68,6 +68,14 @@ class:

$container->setDefinition('newsletter_manager', $definition);

.. note::

When creating a service through a factory, the value chosen for the ``class``
Copy link
Contributor

Choose a reason for hiding this comment

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

when using a factory to create services, the ....

Copy link
Member Author

Choose a reason for hiding this comment

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

Much better! Thanks.

@wouterj
Copy link
Member

wouterj commented Feb 19, 2015

Looks good to me 👍


When using a factory to create services, the value chosen for the ``class``
option has no effect on the resulting service, since the actual class name
only depends on the object returned by the factory. However, the configured
Copy link
Member

Choose a reason for hiding this comment

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

I would split the first sentence:

When using a factory to create services, the value chosen for the class option has no effect on the result srvice. The actual name only depend on the object that is returned by the factory. [...]

Copy link
Member Author

Choose a reason for hiding this comment

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

👍 Short sentences are always better. Fixed. Thanks!

@xabbuh
Copy link
Member

xabbuh commented Feb 19, 2015

Nice 👍

@weaverryan
Copy link
Member

Agreed! It's basically tech-doc poetry :). Nice work Christian and Javier!

@weaverryan weaverryan merged commit 2551322 into symfony:2.3 Mar 14, 2015
weaverryan added a commit that referenced this pull request Mar 14, 2015
…ed via factories (javiereguiluz)

This PR was merged into the 2.3 branch.

Discussion
----------

Added a note about the class option of the services defined via factories

| Q             | A
| ------------- | ---
| Doc fix?      | no
| New docs?     | yes
| Applies to    | 2.3+
| Fixed tickets | #4368

The original comment by @xabbuh in #4368 explained everything so well, that I decided to just copy it.

Commits
-------

2551322 Rewording
90956cc Minor rewording
477da91 Minor rewording
27ca372 Added a note about the class option of the services defined via factories
@javiereguiluz javiereguiluz deleted the fix_4368 branch January 3, 2018 16:33
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.

5 participants