cfml

hey people, I’ve been working on a fork <https://github.com/cfmleditor/cfmleditor> of the vscode extension <https://github.com/KamasamaK/vscode-cfml> and thought I’d try share some things along the way. The Auto Tag Close extension contains some RegEx that can crash the extension thread / worker, the latest version of <https://github.com/cfmleditor/cfmleditor> hopes to eliminate this crash with built in auto tag close, some different regex / search code and some restrictions on the range of the search. In short, my recommendation is uninstall the Auto Tag Close extension if you’re using it

I welcome any new extensions/forks in the CF space, but I am curious, have you reached out to KamasamaK to see about collaborating on his existing extension?

This project has been quite time sensitive, I have reached out to those interested in collaborating

Some of use use the auto close-tag extension for regular HTML too, so are the core HTML tags covered by what you are building into the cfmleditor?

<@U06V7RHE1> my understanding is that HTML files seem to auto close tags already, and html in CFM / CFC files would be covered by the cfmleditor

I can only suggest trying it out and if it doesn’t work to your liking, let me know, if I have the time to fix it I will, otherwise other peoples involvement is welcomed assuming it doesn’t slow progress

VSCode gets a bit of a bad wrap because various extensions can cause some features to stop working and require you to restart the editor

my current list of priorities are
1) stability & performance over features (even current ones might be limited or able to be disabled)
2) Live Share compatibility ( including basic functionality / access to the extension on <http://vscode.dev|vscode.dev> )
3) convince my boss that this is a maintainable codebase.

image.png

an example of something that can be disabled that might have unexpected results, but improves performance on larger files quite drastically.