Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.0-beta-4
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Says Joe.
Activity
Joe, can you fill in some more info here?
Aslak Hellesøy
added a comment - Joe, can you fill in some more info here? Aslak Hellesøy
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Joe Walnes [ jwalnes1 ] | |
| Status | Unassigned [ 1 ] | Assigned [ 2 ] |
Short version:
A method that verifies that all registered components can have their constructors resolved, without actually instantiating them.
Long version:
As we add components/dependencies to our system, one of the things we often forget is to modify the pico config file, which results in an error only caught when we instantiate the container (and because we have many apps sharing the same components this often isn't caught until much later).
So, as one of the integration tests we've added something that instantiates the container heirachies to test all the dependencies can be resolved. However, the side effect of this is that some of our components are heavyweight and we don't want them to be instantiated from this test. So, we need a way to verify dependencies without actually instating the components.
Joe Walnes
added a comment - Short version:
A method that verifies that all registered components can have their constructors resolved, without actually instantiating them.
Long version:
As we add components/dependencies to our system, one of the things we often forget is to modify the pico config file, which results in an error only caught when we instantiate the container (and because we have many apps sharing the same components this often isn't caught until much later).
So, as one of the integration tests we've added something that instantiates the container heirachies to test all the dependencies can be resolved. However, the side effect of this is that some of our components are heavyweight and we don't want them to be instantiated from this test. So, we need a way to verify dependencies without actually instating the components. Joe Walnes
made changes -
| Assignee | Joe Walnes [ jwalnes1 ] | Aslak Hellesoy [ rinkrank ] |
Aslak Hellesøy
made changes -
| Status | Assigned [ 2 ] | In Progress [ 3 ] |
Fixed. Will check in as soon as my PC gets near a LAN.
Aslak Hellesøy
added a comment - Fixed. Will check in as soon as my PC gets near a LAN. Aslak Hellesøy
made changes -
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | 1.0 [ 10145 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
Aslak Hellesøy
made changes -
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Resolution | Fixed [ 1 ] |
Aslak Hellesøy
made changes -
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | 1.0 [ 10145 ] | |
| Fix Version/s | 1.0-beta-4 [ 10412 ] |
what does the method do? i can't find an implementation of it anywhere.