Feature #23
Implement "context" support
Status: | Resolved | Start date: | ||
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | Robert Lemke | % Done: | 0% |
|
Category: | - | |||
Target version: | - | |||
PHP Version: | Complexity: | |||
Has patch: |
Description
It should be possible to put FLOW3 into different environment contexts. Examples are "optimized", "production", "development" and "testing".
Other parts may then behave accordingly, for example the AOP would adjust the caching of the proxy classes depending on the selected mode.
See also #339 about Components.ini format.
Associated revisions
- FLOW3: (Reflection) Added getProperty() to T3_FLOW3_Reflection_Class. Fixes #370.
- FLOW3: (Cache) Implemented load() support for the File backend. Addresses #368.
- FLOW3: (Component) The component manager's default context is now "Development". Relates to #23.
- Testing: The Base Testcase now sets the cloned component manager's context to "Testing".
History
#1 Updated by Robert Lemke over 7 years ago
- Target version changed from 2 to 1
#2 Updated by Robert Lemke over 7 years ago
- Subject changed from Create "environment mode" support to Implement "context" support
#3 Updated by Robert Lemke about 7 years ago
- Target version deleted (
1)
#4 Updated by Robert Lemke almost 8 years ago
- Status changed from New to Resolved