VSCode Extension: ConfigurationProvider - Configuration Section naming

[jmenzies12]

Hey there,

In order for the ConfigurationProvider to pick up properties registered in the package.json for the extension and map them to the language, the properties have to be explicitly named with the language name at the start i.e. "argument.blah.blah".

However we have multiple languages registered under our extension, to keep inline with naming conventions it would make sense for our properties to start with the extension name followed by the language name.

Would it be possible to make the section name configurable?

Cheers
Jonathan

[msujew]

Hey @jmenzies12,

I think you can just override the DefaultConfigurationProvider (or create a completely new implementation of ConfigurationProvider) for your language server. In your override, you can define any convention you like.

See also for binding:

langium/packages/langium/src/services.ts

Lines 112 to 115 in efb6c9e

	export type LangiumDefaultSharedCoreServices = {
	readonly ServiceRegistry: ServiceRegistry
	readonly workspace: {
	readonly ConfigurationProvider: ConfigurationProvider