Mach-II/Mach-II-Framework — Issue #19: Move framework configuration properties into a Property.cfc
Author: mpwoodward
Created: 2012-03-01 00:52:28+00:00
State: open
Labels: enhancement

(Moved from http://trac.mach-ii.com/machii/ticket/144)

I was thinking that it might be a good idea to refactor the framework specific properties (such as applicationRoot, defaultEvent, etc.) into a MachIIConfigurationProperty.cfc. We would still support the old fashion way of doing things, but add all new functionality through MachII.properties.MachIIConfigurationProperty. I've targeted this for 1.8. Thoughts?

Changed 3 years ago by kurtwiersma

I agree that this does make sense to do as part of 1.8.

comment:1 Changed 3 years ago by kurtwiersma

Milestone changed from Uncategorized to Mach-II 1.8.0 alpha
comment:1 Changed 3 years ago by peterfarrell

I was thinking that we're going to have to support the old properties for BC and ultimately mirror the values set the configuration property into the old property names. However, I'm wondering if this is a good idea. A person will be able to register the property.cfc with any name they choose. We'll have to find the ConfigProperty?.cfc to leverage the data it contains. I guess I'm wondering what we gain by adding this other than easier maintenance for us. I guess it's better encapsulation for us and ultimately look better in the xml. I guess we could easily put in a getter/setter called getConfig() in which we can reference the configuration property cfc. Thoughts?

comment:2 Changed 3 years ago by peterfarrell

hours set to 0
estimatedhours set to 0
totalhours set to 0
billable set to 1
I'm not sure if this is feasible or worth the effort because we still need to support the current properties for BC. It's not like we have 500 properties. Thoughts?

comment:3 Changed 3 years ago by peterfarrell

Version changed from 1.8.0 to Uncategorized
Milestone changed from Mach-II 1.8.0 alpha to Uncategorized