[Extendable Param Files] Intellisense for shared .bicepparam files

[stephaniezyen]

Add intellisense in VSC for shared .bicepparam files

[slavizh]

+1

[polatengin]

hey @stephaniezyen , @slavizh , can you elaborate a little bit and help me to understand what areas we need intellisense, please?

[slavizh]

@polatengin I guess the simplest example that we can take from https://github.com/Azure/bicep/blob/main/docs/experimental/extendable-param-files.md where if we edit root.bicepparam and start typing param to get suggestion that namePrefix, location and tags parameters. This is assuming that leaf.bicepparam already have using statement pointing to bicep modile and extends to root.bicepparam. Of course the intellisense spread across all other cases where you might have complex objects and arrays under the parameter. Also if we take example like:

// shared.bicepparam
using none

param myApp = {
  name: 'demo'
  diagnosticSettings: {
     resourceGroup: 'myRg'
     name: 'workspace0001'
  }
}

// child.bicepparam
using './main.bicep'
extends './shared.bicepparam'

param app = {
  name: base.myApp.name
  diagnosticSettings: base.myApp.diagnosticSettings
}

Once the base is configured in child.bicepparam when you open shared.bicepparam and hover over name or diagnosticSettings properties you should the descriptions for them as you are in file child.bicepparam and hovering them there and getting the information from main.bicep. Even if hovering over myApp.diagnosticSetttings.name in shared.bicepparam file you should see the description of if it as defined in main.bicep via user defined data types.