This one is tricky because the config allows any number of user-defined pools, and this config defines the valid settings in each "pool" scope. So I'm thinking something like:
define azure batch pool config as an "array" config scope
if a config option doesn't match a scope (e.g. azure.batch.pools.foo, remove the last name and see if it matches an array scope (azure.batch.pools)
use the array scope to provide validation, hover hints, completions
Alternatively, it might be time to refactor the config schema into a proper tree structure, where each node can contain options, scopes, or an array of scopes.
This one is tricky because the config allows any number of user-defined pools, and this config defines the valid settings in each "pool" scope. So I'm thinking something like:
azure.batch.pools.foo, remove the last name and see if it matches an array scope (azure.batch.pools)Alternatively, it might be time to refactor the config schema into a proper tree structure, where each node can contain options, scopes, or an array of scopes.