tracker issue : CFB-4198226

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

Fix for issue CFB-4188240 is incomplete: var keyword still breaks formatter

| View in Tracker

Status/Resolution/Reason: To Fix//

Reporter/Name(from Bugbase): Legorol San / Legorol San ()

Created: 07/02/2017

Components: Editor Features, Code Formatting

Versions: 2016,3.2

Failure Type: Non Functioning

Found In Build/Fixed In Build: Update 4 /

Priority/Frequency: Major / All users will encounter

Locale/System: UK English / Windows 10 64 bit

Vote Count: 1

The fix for CFB-4188240 was supposedly included in Coldfusion Builder 2016 Update 4, however it does not actually fix the issue. The code formatter still can't format most code that include the 'var' keyword in cfset.

Consider reopening CFB-4188240.

I have installed the update, and have observed the following. Some progress has been made. For example, this code can now be formatted:
<cffunction name="f">
<cfset var x=1>

However, these code examples still can't be formatted:

Example 1:
<cffunction name="f">
<cfset var x=1>
<cfset var y=2>

Example 2:
<cffunction name="f">
<cfargument name="y">
<cfset var x=1>

Example 3:
<cffunction name="f">
<cfset x=1>
<cfset var y=2>



Is this going to be fixed any time soon? I originally reported this in CFB-4188240 in Sept 2016, it's been over a year and a half since. Code formatting is one of the few features included in the PAID version of ColdFusion Builder (as opposed to the free express version), and was one of the main reasons for us for paying for a license.
Comment by Legorol San
27893 | May 20, 2018 12:28:01 PM GMT
+1 - Please prioritize formatting and colorization tickets. There should be zero issues w/ those.
Vote by Aaron Neff
29494 | August 15, 2018 04:50:16 AM GMT
Adobe, any news on this? It's been more than 2 years since I've originally reported this bug. Even CFB 2018 has been out for a while and it has the same problem. The 'var' keyword is ubiquitous. We use it in every piece of CF code we write, as we should and have done for many years. It is not acceptable that it breaks a paid feature in CFB. Even a single 'var' keyword somewhere in a .cfm or .cfc breaks formatting for the entire file, including all UDFs. Code formatting is a highlighted feature on and is essentially unusable. This should be classed a critical, high priority issue.
Comment by Legorol San
29998 | December 04, 2018 01:14:36 PM GMT
Hi Adobe, The breadth of CFB's basic formatting and colorization issues, combined w/ the lack of CFB prereleases, tells a story. Can we improve that story? Thanks!, -Aaron
Comment by Aaron Neff
30000 | December 04, 2018 07:50:03 PM GMT