StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16971675
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-06T20:34:18.913
FavoriteCount
0
LastActivityDate
2013-06-06T20:34:18.913
LastEditDate
LastEditorUserId
0
OwnerUserId
658091
ParentId
16947427
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
From my understanding in Silex/Symfony2, is that there is no 'magical way' to do these type of things. For my first question: It is allowed to add objects that are created before the container. In Symfony2, in <code>Kernel:initializeContainer</code> function, Kernel adds itself to the container (<code>$this->container->set('kernel', $this);</code>) and later on, in the xml files, services are injected with Kernel (<code><argument id="kernel" type="service" /></code>). In Silex, <code>Application:__construct</code> function creates and adds objects to the container. <code>Application</code> injects itself to the <code>ServiceProviders</code>, so these providers can inject dependencies to their objects and add them to the container. <code>$container->manualAdd('_logger', $logger);</code> is correct. <hr> For my second question: depends on how I want to handle it. I came up with 3 options: .1 For C#-event-like, <code>Kernel</code> is added into the container: In ComplexClass: <code>kernel.terminate += kernelTerminate</code> .2 EventDispatcher (as long as <code>EventDispatcher</code> class doesn't need dependencies that are created in the xml files) <pre><code>//bootstrap function: $dispatcher = new KernelEventDispatcher(); $kernel = new Kernel($dispatcher); $container->manualAdd('_kernel.dispatcher'); </code></pre> . <pre><code> <argument id="_kernel.dispatcher" type="service" /> </code></pre> .3 Create an object that implements an interface: (I couldn't find another name for <code>Runnable</code>) <pre><code> <service id="complex_class_runnable" class="ComplexClassRunnable"> <argument type="service" id="complex_class" /> <argument type="service" id="_kernel" /> </service> </code></pre> . <pre><code>//in ComplexClassRunnable $kernel->addRunnable($this); </code></pre> . <pre><code>//in Kernel foreach($this->runnables as $runnable){ $runnable->init(); //same for terminate } </code></pre> Bootstrap updated: <pre><code>function bootstrap($file = 'file.xml'){ $logger = new Logger(); $logger->log('bootstrap: init'); $kernel = new Kernel($logger); $container = new DIContainer(new ConfigReader($file), $logger); $container->manualAdd('_kernel', $kernel); $container->manualAdd('_logger', $logger); $container->build(); $kernel->boot(); $logger->log('bootstrap: terminate'); } class DIContainer{ public function build(){ //read xmls and create classes, etc. $this->logger->log('DIContainer: creating objects: {objects}'); } } class Kernel{ public function boot(){ //... } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POphp dependency injection with a container
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOsakaHQ
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POphp dependency injection with a container
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.