Modify ↓
#12924 closed enhancement (fixed)
Eliminate EnvironmentSetup class
Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Milestone: | 1.3.3 |
Component: | general | Version: | |
Severity: | normal | Keywords: | refactoring |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Follow-on to #12891. At one time the EnvironmentSetup
class contained a lot of code, but we've done a lot of refactoring since: EnvironmentSetup in Trac 1.0 vs EnvironmentSetup in Trac 1.3.2.
- I think it makes sense to eliminate the
EnvironmentSetup
class created in r1840 and implementIEnvironmentSetupParticipant
onDatabaseManager
. - In r1840 the
IEnvironmentSetupParticipant
for attachments and templates were added, and the environment directories for attachments and templates were created in theIEnvironmentSetupParticipant.environment_created
implementations. This was changed for attachments in r11169, but persists for templates. I think it's more clear to have all the top-level environment directories created inEnvironment.create
.
Attachments (0)
Change History (3)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Keywords: | refactoring added |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Fixed indentation error in Chrome.environment_created
and committed to trunk in r16341.
Note:
See TracTickets
for help on using tickets.
Proposed changes in log:rjollos.git:t12924_refactor_environment_setup.