i've skimmed the documentation-linked pdf for the ...
# adobe
w
i've skimmed the documentation-linked pdf for the vscode plugin and didn't find any info on whether this extension does or does not play nicely with the de facto cfml extension already out there. any information as to whether other cfml extensions need to be uninstalled or not?
r
It doesn't appear to since it's using its own language server. However, it did clobber my theme customizations. 😞
m
uh-oh. yeah, all vscode plugins should play nicely in the sandbox with the other children. I'm just installing now, but I hope it doesn't try to "take over" vscode, since I use vscode for projects that aren't CF related as well
r
FYI, it modifies the theme customizations any time you change any extension setting, not just on install.
m
picard facepalm here
it would probably be good to mention that changing extension settings triggering the bug again so it doesn't get fixed just for the install but not for the settings change case
m
Do any of the settings for the extension affect it or does it just always overwrite with the same thing?
r
It always overwrites with the same thing.
m
a bit odd, since I'd think the plugin would be functionality rather than theming (unless what they're aiming for is theming just the bits this particular extension itself adds)
r
The extension removed theme customizations that are unrelated to the extension. The extension shouldn't touch theming at all.
m
And according to the bug report, it's even overriding the setting globally instead of limiting it to
cfml
tokens.
r
Correct, but that's the way VSCode is designed. Adobe really just needs to offer a separate theme extension that is recommended to install along with the Adode CFML extension.
m
That's not an excuse. They only have 4 distinct scopes that match that, so they could have specified them exactly.