Create a specialized langage id for adx template json files, and configure our custom language server with that, instead of piggybacking on the default json language server.
This does mean that the prettier vscode extension won't currently work against our adx-template-json files, since it keeps the vscode language ids in the base prettier code base, so I can't configure it here in our extension. We'll address that later; for now, this supports default vscode-based formatting for template json files, sharing the json formatting configuration properties.
What does this PR do?
Create a specialized langage id for adx template json files, and configure our custom language server with that, instead of piggybacking on the default json language server.
This does mean that the prettier vscode extension won't currently work against our adx-template-json files, since it keeps the vscode language ids in the base prettier code base, so I can't configure it here in our extension. We'll address that later; for now, this supports default vscode-based formatting for template json files, sharing the json formatting configuration properties.
What issues does this PR fix or reference?
Fixes #5