Skip to content

Adding a tip on using doctrine as a service #2234

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

Conversation

richardmiller-zz
Copy link
Contributor

Q A
Doc fix? no
New docs? yes
Applies to all
Fixed tickets #2224

As discussed in GH-2224.

@wouterj
Copy link
Member

wouterj commented Feb 11, 2013

The #2224 issue should be added to the Q/A table (in the last row), as this PR fixes that issue.

I think we should do this for the other book articles. For instances, a note about the templating service in book/templates, the form.factory service in book/forms and I think propel has services too?

@richardmiller-zz
Copy link
Contributor Author

I think it is worth doing for those articles as well. @weaverryan what do you think?

weaverryan added a commit that referenced this pull request Feb 19, 2013
Adding a tip on using doctrine as a service
@weaverryan weaverryan merged commit 1016517 into symfony:2.0 Feb 19, 2013
@weaverryan
Copy link
Member

Hi guys!

In general, the conversation in #2224 makes sense to me, and I'm a fan of mentioning which services we're working with somewhere near where we're working with them. Hopefully this will help a bit :).

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants