I was investigating why code-server was not picking up the settings/extensions from vscode-syncing.
It turns out that the path building logic is completely different between them - vscode-syncing vs code-server.
I've tried to keep my changes minimal and redid my previous changes to prevent a clash between the Coder's platform vs Coder's code-server. I also built and tested these changes locally, so I can confirm they work across my official vscode and remote code-server setup. I can confirm that VSIXs downloaded from the marketplace do work on code-server.
Follow-up to https://github.com/nonoroazoro/vscode-syncing/pull/94:
I was investigating why code-server was not picking up the settings/extensions from vscode-syncing. It turns out that the path building logic is completely different between them - vscode-syncing vs code-server.
I've tried to keep my changes minimal and redid my previous changes to prevent a clash between the Coder's platform vs Coder's code-server. I also built and tested these changes locally, so I can confirm they work across my official vscode and remote code-server setup. I can confirm that VSIXs downloaded from the marketplace do work on code-server.
Do let me know what you think!