8000 DI Definition by l3ackslash0 · Pull Request #2941 · symfony/symfony-docs · GitHub
[go: up one dir, main page]

Skip to content

DI Definition #2941

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

Closed
wants to merge 4 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions glossary.rst
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,16 @@ Glossary
selection of bundles, a sensible directory structure, a default
configuration, and an optional configuration system.

Dependency Injection
The Dependency Injection is a design pattern highly used in the Symfony2 Framework.
It encourages loosely coupled and more maintainable architecture of an application.
The main principle of this pattern is that it allows developers to *inject* objects
(also known as services) in other objects, generally passing them as parameters.
Different levels of coupling between these objects can be established
depending on the method used to inject objects together.
The Dependency Injection pattern is the more often associated
to another specific type of object: the :doc:`/book/service_container`

Project
A *Project* is a directory composed of an Application, a set of
bundles, vendor libraries, an autoloader, and web front controller
Expand Down
0