Remove quarkus-properties language and collect document selectors from extensions

[xorye]

Fixes #3

Signed-off-by: David Kwon dakwon@redhat.com

[xorye]

To test this PR:

• package this PR into a vsix and install
• checkout Define Quarkus document selector and TextMate grammar vscode-quarkus#294 and start vscode-quarkus (either start it from sources or install it as a vsix, it doesn't matter)
• open a Quarkus application.properties file (make sure that the languageId is quarkus-properties) and invoke completion. Since the file's language is quarkus-properties, the textdocument/completion request should be sent to the MP language server, and completion items should be returned.

[rzgry]

Looking at the schema It looks like this provides a vscode extension the ability to provide a single document selector. Would their ever be a use-case where an extension would need to provide multiple document selectors?

[xorye]

Looking at the schema It looks like this provides a vscode extension the ability to provide a single document selector. Would their ever be a use-case where an extension would need to provide multiple document selectors?

@rzgry thanks for the review, I will make changes.

Also, to be consistent with https://github.com/microsoft/vscode-languageserver-node/blob/3eddc56d9491b6f97c5e82242a3a14421d42bea1/protocol/src/common/protocol.ts#L74, I will add pattern as a possible field.

[xorye]

@rzgry @datho7561 if there aren't any more changes to be made, I'd like to merge this soon. Please let me know, thanks!

[xorye]

For some reason, the client/registerCapability request for range formatting has quarkus-properties appearing twice:

MicroProfile Tools server trace:

[Trace - 11:16:26 a.m.] Received request 'client/registerCapability - (8)'.
Params: {
    "registrations": [
        {
            "id": "61e7b5ba-a567-4415-8817-70e18fed36a9",
            "method": "textDocument/rangeFormatting",
            "registerOptions": {
                "documentSelector": [
                    {
                        "language": "microprofile-properties"
                    },
                    {
                        "language": "quarkus-properties"
                    },
                    {
                        "language": "quarkus-properties"
                    }
                ]
            }
        }
    ]
}

I don't think its caused by this PR though. I'm investigating.

[xorye]

It's not caused by this PR, this still happens in the 1.6.0 vscode-quarkus release. I made an issue about this: redhat-developer/vscode-quarkus#296