Ignoring blocks/tags via settings vs comment about commandbox-cfformat HOT 2 OPEN

I’d go a little further and say these script blocks shouldn’t exist in the cfm files either… that’s what .js files are for :-) Unfortunately, it’s a scattered legacy monolith.

My original thought was just a setting to ignore script blocks (off by default to keep the current behavior). I only expanded to the regex because I recalled cfformat doing the same to some XML and the regex approach should cover that too.

we’ll just have to be more diligent in code reviews until things get a bit cleaner in the app.

thanks for cfformt!

from commandbox-cfformat.

I agree this is a problem, and is one of the reasons my focus with this library was on component files where <script> tags are not likely to be found (though of course it does happen). The mixture of CFML and JavaScript makes things tricky. I am not sure yet which approach to solving this is the most doable. Whatever is done is most likely always going to be imperfect, but I do think things can be improved.

from commandbox-cfformat.