- Using the sugar added in the previous item
- Test when Model::Foo depends_on Model::Bar
+ - Tests for using the container outside of Catalyst
+ - Custom container which adds some (very simple) services which are initialized from
+ the application config file (note plain services, not components)
+ - Depend on (and test) these inside Catalyst
+ - Test loading container outside Catalyst, and these services working
+ - Test Catalyst / MyApp is not loaded
#### Extending my app, notes
### To polish off / t0m review
- - + $class->container->get_sub_container('model')->make_single_default;
- + $class->container->get_sub_container('view')->make_single_default;
-
- get_components_names_types
-
- locate_components
-
- +# FIXME - t0m, how do you feel about this name?
- +# also, do you think I should draw it here, or just return the data structure?
- +sub get_components_names_types {
-
+Same as L<build_model_subcontainer>, but for controllers. The difference is
+that there is no ACCEPT_CONTEXT for controllers.
^^ This is wrong!!
- my $accept_context_args = $self->param('accept_context_args');
+ my $accept_context_args = $params{accept_context_args};
- ^^ This is wrong! The service should be allowed to mangle the accept_context args, no?
+ ^^ This (may be) wrong! I am thinking the service should be allowed to mangle the
+ accept_context args, no?
Without this change, the user could make a custom service which mangled the param, and use
Catalyst/IOC/Service/WithAcceptContext.pm, with this change, that module will always see the
- un-mangled version??
-
- accept_context_args - where does this come from?
-
- + $purity = $purity // 1;
- ^^ perl 5.10 only
+ un-mangled version?? However, without this change, shit doesn't work...
### Known issues
- expand_component_module
+ - People wrapping locate_components in Catalyst.pm