tracker issue : CF-3712059

select a category, or use search below
(searches all categories and all time range)

Implement feature toggling

| View in Tracker

Status/Resolution/Reason: Closed/Deferred/

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 02/21/2014

Components: Core Runtime

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: PublicBeta /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 0


ColdFusion desperately needs a feature toggling mechanism so things like isValid(), ?: and isNull() can be safely fixed without the perennial Adobe excuse of "can't because backwards compatibility".

The feature toggle should control the behaviour of old buggy code: either the new fixed version is used (default), or the behaviour can be toggled to use the old buggy version, for the sake of "backwards compatibility"

We need to get the language moving forward, not wallowing around in old broken versions.


----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3712059

External Customer Info:
External Company:  
External Customer Name: Adam Cameron.
External Customer Email:  
External Test Config: My Hardware and Environment details:



Oh, forgot to mention: any usage of toggled "bad" functionality should be logged as a warning to stderr. -- Adam
Comment by External U.
13362 | February 21, 2014 07:54:11 PM GMT
Passing bug to management team for review (Comment added from ex-user id:vnigam)
Comment by Adobe D.
13363 | February 23, 2014 11:55:17 PM GMT
Since this request is little generic, can you explain what exactly you mean? There are many settings on the application/server which toggle the behavior of a feature.
Comment by Rupesh K.
13364 | March 03, 2014 11:53:12 PM GMT
I mean a general approach to facilitate being more aggressive about fixing bugs without you guys being able to fall back on "backwards compat". Obviously the technique is generally used to apply to the control of features-in-development, but it can be extended to cover in-place features too. Currently you just have a new randomly managed setting (neo-runtime.xml, CFAdmin, Application.cfc, attribute on the tag or argument on the function) when you do stuff like this. I'm suggesting taking a coherent uniform approach. -- Adam
Comment by External U.
13365 | March 10, 2014 10:08:43 AM GMT
This is not planned for this release.
Comment by HariKrishna K.
13366 | December 08, 2014 06:37:33 AM GMT