VS Code Local files.associations Setting Not Propagated to Remote‑SSH Host
The goal is to have a custom file extension, such as *.foo, recognized as JavaScript both when editing files locally in VS Code and when the same workspace is opened through the Remote‑SSH extension on a production Linux host. Locally, adding "*.foo": "javascript" to the files.associations setting activates the correct language mode, but when connecting via
vscode