When validating that our settings are not overridden by a user's ssh config, we were converting host names to regular expressions to use as matchers. In doing so, we were not correctly escaping. characters, which are special in regular expressions but not in host names.
This triggered a false flag when using the vscode extension alerting the user they were improperly overriding settings which they were not.
Note: this didn't come up before because we only now started usingcoder. has a host name in the ssh config as part of updating the vscode extension to simply usecoder ssh as opposed to a dedicatedcoder vscodessh command.